Skip to main content
Glama

Related Servers

Alternatives to danke-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to send and receive Bitcoin over the Lightning Network using NWC or LND backends.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server giving AI agents Bitcoin and Lightning superpowers for price checks, mempool inspection, Lightning payments, and more.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP 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.
      17
      9
      MIT

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues