Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Agentic AQUA

No user-submitted related servers found.

    Related Servers

    • Agentic AQUA

      jan3dev
      A
      license
      B
      quality
      B
      maintenance
      MCP server for managing Bitcoin, Liquid Network, and Lightning wallets through AI assistants, with unified seed support, secure encrypted storage, and both CLI and tool interfaces.
      73
      6
      MIT

    • btc-mcp-srv

      lightphon
      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

    • bitcoin-mcp

      spcpza
      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.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 79 tools

    Disambiguation3/5

    Tools are grouped by provider prefixes, but multiple parallel swap stacks (SideShift, Changelly, SideSwap) each expose near-identical quote/send/receive/status tools, forcing the agent to rely on long descriptions and the two *_recommend helpers to choose correctly. Similarly, Lightning swap status vs lw_tx_status vs sideswap_swap_status, and btc_balance vs lw_balance vs unified_balance, require careful reading. Descriptions do disambiguate, but overlap is substantial.

    Naming Consistency4/5

    A predictable provider-prefix convention (lw_, btc_, lightning_, sideshift_, sideswap_, changelly_, wapupay_, jan3_, pix_, qr_) is applied consistently across the whole surface. Within each prefix, verb/noun ordering varies (lw_create_wallet vs btc_balance vs lw_transactions), which is a minor deviation but still readable.

    Tool Count2/5

    79 tools is far too many for a single server; even with the broad scope (multi-chain wallet, four swap/ramp providers, PIX, JAN3 identity, QR utilities), the surface is unwieldy and pushes the agent toward tool-selection errors. Each grouping is defensible, but the aggregate is well past a reasonable ceiling.

    Completeness4/5

    Coverage is genuinely deep: wallet create/import/export/backup/delete, send/sweep, unified balances, swap quote→execute→status→refund for each provider, plus fiat on/off ramps and auth lifecycle. Minor gaps remain (e.g. no explicit fee-estimation or Lightning receive tool outside the JAN3 address flow), but agents can work around them.

    Resources