Lightning Wallet MCP
Related Servers
Alternatives to Lightning Wallet MCP
- AlicenseBqualityFmaintenanceEnables interaction with lightning addresses and common lightning tools via your LLM, providing Lightning Network functionality through natural language.33 npm1MIT
- 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
Related Servers

PayAgents MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to autonomously make policy-controlled payments for APIs and tools via Bitcoin Lightning (L402) and Base USDC (x402), including paying paywalled endpoints, checking balances, and reviewing transactions.314 npmMIT- AlicenseAqualityBmaintenanceL402 + x402 client MCP. AI agents discover, pay for, and consume any payment-gated API autonomously. Supports Lightning (NWC), Cashu ecash, stablecoins, and human-in-the-loop payments.14463 npmMIT

wdk-wallet-liquid-mcpofficial
FlicenseAqualityCmaintenanceEnables AI agents to interact with a Liquid network wallet, including balance checks, transaction history, and sending L-BTC or Liquid assets. Backed by an in-process LWK wallet, requiring only a mnemonic, with both stdio and HTTP support.10-- AlicenseNot gradedqualityDmaintenanceEnables Bitcoin Lightning wallet integration with LLMs through Nostr Wallet Connect (NWC). Supports lightning payments, LNURL operations, and L402 authentication for AI-powered bitcoin transactions.22 npmApache 2.0
- AlicenseAqualityDmaintenanceEnables AI agents to perform Bitcoin and Lightning Network payments using a non-custodial, zero-trust architecture. It provides 13 tools for wallet management, invoice creation, and payment processing while keeping node credentials local to the user's machine.139 npmMIT

token4u-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to call LLM APIs via x402 micropayments in USDC on Base network, manage a local wallet, and query consumption records.335 npmMIT
TDQS
Scored across 54 tools
Most tools have clear distinct purposes, especially within the arena, board, and webhook clusters. However, several payment and fund-movement tools overlap in user intent—such as create_invoice vs get_deposit_invoice and fund_agent vs transfer_to_agent—and rely heavily on descriptions to disambiguate.
The majority of tools follow a clear verb_noun or module_verb pattern (e.g., create_invoice, list_agents, arena_play, board_post), all in snake_case. Minor deviations like whoami and keysend prevent a perfect score but do not create real confusion.
With 54 tools, this far exceeds the 25-tool threshold and falls into the extreme 50+ category. The server bundles wallet operations, account management, agent management, webhooks, Nostr, a message board, and a tournament arena into one surface, making it a very heavy tool set.
The server provides thorough coverage of its broad domain: invoice lifecycle, payment methods, withdrawals, account and agent management, budgets, webhooks, Nostr identity/zaps, board interactions, and arena participation. No glaring dead ends or missing core operations are apparent.