lightning-mcp
Related Servers
Alternatives to lightning-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that enables AI agents to make autonomous Bitcoin Lightning Network payments using the L402 protocol. Agents can pay for API access, purchase resources, and complete transactions without human intervention — invoice comes in, sats go out, done.179MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to send and receive Bitcoin over the Lightning Network using NWC or LND backends.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.119 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server giving AI agents Bitcoin and Lightning superpowers for price checks, mempool inspection, Lightning payments, and more.MIT

zunivo-mcpofficial
AlicenseAqualityCmaintenanceMCP server that lets AI agents discover and pay for .agent services using USDC over x402, with daily budget controls and payment link creation.613 npmMIT- AlicenseBqualityDmaintenanceAn MCP server to provide AI agents money functionalities via Nostr and Cashu.651 npm17MIT
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: single vs batch payments, invoice vs address handling, and resolution vs payment are all separated by explicit resource and action. No two tools can be easily confused for the same task.
All tool names use snake_case and follow a verb_noun pattern (e.g., resolve_lightning_address, pay_invoice, create_invoice, check_balance). Compound nouns like lightning_address and l402 are handled consistently.
11 tools is well-scoped for a Lightning wallet plus Nostr discovery/trust consumer agent. Every tool covers a distinct operation without redundancy or trivial filler.
Core consumer workflows are covered: balance, invoice creation/decoding/payment, address resolution/payment, batch payments, L402 access, and Nostr trust/service discovery. Minor gaps exist, such as invoice status queries, transaction history, and write operations for trust attestations or service publication.