No user-submitted related servers found.
Scored across 55 tools
Tools are mostly distinct by resource and action, with clear descriptions for similar operations like invoice creation and payment. Some pairs (get_account_info vs get_wallets, send_to_wallet vs send_to_username) overlap slightly, but their descriptions specify exact use cases, minimizing misselection. Overall, an agent can reliably pick the correct tool.
The tool names consistently use snake_case with a verb_noun pattern (get_, create_, pay_, send_, estimate_, subscribe_, cancel_). Minor inconsistencies include list_webhooks vs get_wallets for retrieval, and check_username_available/lookup_user_wallet using non-get verbs. These are understandable but break the pattern slightly.
With 55 tools, the server has an extremely large surface area. While the domain (Lightning wallet, invoices, onchain, L402, subscriptions) is broad, 55 tools exceed the 'too many' threshold and can overwhelm agents. Many tools are variants (e.g., create_invoice, create_invoice_usd, create_invoice_no_amount), making the set feel bloated.
The server provides comprehensive coverage of the wallet domain: account management, invoice lifecycle, payment methods, on-chain operations, intraledger transfers, fee estimation, webhooks, real-time subscriptions, and L402 paywalled access. There are no obvious gaps or dead-end operations; all critical workflows are supported.