Skip to main content
Glama
dhyabi2

nano-mcp

by dhyabi2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nano-mcp

No user-submitted related servers found.

    Related Servers

    • nano-mcp

      PANDeveloper001
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to hold XNO and make feeless, instant per-API-call payments via the public rpc.nano.to node, including wallet management, paid tool execution, and a self-hostable x402 payment facilitator.
      7
      MIT

    • Nano MCP Server

      nano133-com
      A
      license
      A
      quality
      B
      maintenance
      Gives AI agents tools to read Nano (XNO) accounts and history, get XNO/USD rates, create invoices with unique amounts, and verify or wait for payments — with receiving requiring no key. Optionally enables sending small amounts from an off-by-default, capped wallet with an allowlist, daily limits, and exactly-once idempotency keys.
      10
      MIT

    • Nano Currency MCP Server

      kilkelly
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents using the Model Context Protocol (MCP) to send Nano cryptocurrency and retrieve account/block information via Nano node RPC.
      4
      12 npm
      11
      MIT

    • Nerve RPC MCP

      NerveNetwork
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Nerve blockchain JSON-RPC and REST APIs as MCP tools, enabling AI agents to receive, pay, swap, and query balances with local account management and no gas fees.
      1
      -
    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 7 tools

    Disambiguation4/5

    Most tools target distinct actions: account queries (get_balance/get_history) are separate from the payment flow (quote/quote_usd/verify_payment/pay_and_call). get_address overlaps slightly with the one-time addresses returned by quote tools, and quote vs quote_usd are similar, but the descriptions clarify when each should be used.

    Naming Consistency4/5

    The get_balance/get_history/get_address group follows a clear verb_noun pattern, and verify_payment is similarly structured. quote, quote_usd, and pay_and_call deviate a bit from that pattern but are still lowercase, readable, and verb-first.

    Tool Count5/5

    Seven tools is well-scoped for a Nano payment/call gateway: account lookups, quoting, verification, and execution are covered without redundancy or bloat. Each tool has a clear place in the payment-and-call flow.

    Completeness4/5

    The core lifecycle is present: obtain an address, quote a price, pay, verify payment, and invoke the call, with balance/history utilities for account tracking. There is no explicit request-status or cancel/expiry operation, but agents can work around this via re-quoting or verify_payment's status return.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources