Skip to main content
Glama
Sign In
dhyabi2

nano-wallet

by dhyabi2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to nano-wallet

No user-submitted related servers found.

    Related Servers

    • 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
      9 npm
      11
      MIT

    • pkinative-mcp

      Nizoka
      A
      license
      A
      quality
      A
      maintenance
      Enables inspection and verification of X.509 certificates and chains, CRLs, OCSP responses, CMS signatures and RFC 3161 timestamps, along with issuing certificates and CSRs, decoding ASN.1/PEM/OIDs, and opening PKCS#8 and PKCS#12 files without ever returning a key byte. Runs entirely offline with no network access, exposing 34 tools to any MCP client.
      34
      82 npm
      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 MCP Server

      dhyabi2
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for NANO cryptocurrency operations, enabling AI agents to generate wallets, send/receive transactions, check balances, and more via JSON-RPC.
      6 npm
      3
      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 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action and resource: address creation, address validation, balance query, and receiving funds. There is no overlap in purpose, so an agent can easily select the right tool.

    Naming Consistency3/5

    Tool names mix conventions: create_address and validate_address use verb_noun, while balance is a bare noun and receive is a bare verb. The names remain readable, but the pattern is not fully consistent.

    Tool Count4/5

    Four tools is a tight, reasonable set for a receive-focused Nano wallet, and each tool appears to earn its place. It is slightly thin for a full wallet, but appropriate if the scope is deliberately limited.

    Completeness3/5

    The set covers address creation/validation, balance checks, and receiving funds, but omits sending/spending, transaction history, and broader account management. For a server named nano-wallet, the lack of send capability is a notable gap.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources