danke-mcp
Related Servers
Alternatives to danke-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to send and receive Bitcoin over the Lightning Network using NWC or LND backends.MIT

satsrail-mcpofficial
AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to accept Bitcoin Lightning payments. It allows agents to create orders, generate invoices, check payment status, and manage the full SatsRail merchant API through natural language.MIT- AlicenseBqualityDmaintenanceAn MCP server to provide AI agents money functionalities via Nostr and Cashu.663 npm17MIT
- AlicenseNot gradedqualityDmaintenanceMCP server giving AI agents Bitcoin and Lightning superpowers for price checks, mempool inspection, Lightning payments, and more.MIT
- AlicenseAqualityCmaintenanceMCP 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
- AlicenseAqualityDmaintenanceMCP server that gives AI agents Lightning payments, L402 API access, trust verification, and service discovery.1111 npmMIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: balance checks personal finances, leaderboard shows rankings, profile lookups public data, register handles onboarding, send transfers sats to others, and withdraw handles external payouts. The self vs. other distinction between balance and profile is clearly delineated.
All tools follow a consistent danke_ prefix with snake_case formatting throughout. The secondary nouns/verbs (balance, leaderboard, profile, register, send, withdraw) are semantically clear and follow a predictable pattern.
Six tools is an ideal count for this focused domain. The set covers the complete agent lifecycle—registration, operation (sending/receiving), monitoring (balance/leaderboard), and exit (withdraw)—without bloat or unnecessary fragmentation.
Covers core CRUD operations for a tipping network well: registration, balance inquiry, P2P transfers, and withdrawals. Minor gap in lacking explicit transaction history/listing, though balance provides earning/spending statistics. Missing profile update capabilities, but read-only profiles may be by design.