Skip to main content
Glama
Feeless402

nano-pay

by Feeless402
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to nano-pay

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
    • PipRail by piprail

      PipRailofficial

      piprail
      A
      license
      A
      quality
      A
      maintenance
      A budget-bound x402 payment wallet for AI agents: it autonomously pays HTTP 402 payment-gated URLs across every major chain (EVM, Solana, and many non-EVM families). Self-custodial and backendless, your key, your RPC, with spend caps enforced before any on-chain send.
      8
      9
      MIT

    • agentic-pay

      ShieldCubed
      A
      license
      Not graded
      quality
      C
      maintenance
      Non-custodial payment engine for AI agents supporting BTC, ETH, USDT, USDC, XRP, XMR, and ZEC. Exposes wallet, invoice, and payment tools over MCP with per-agent spend limits, plus x402 pay-per-call support.
      42 npm
      Business Source 1.1

    • 402-mcp

      forgesworn
      A
      license
      A
      quality
      B
      maintenance
      L402 + x402 client MCP. AI agents discover, pay for, and consume any payment-gated API autonomously. Supports Lightning (NWC), Cashu ecash, stablecoins, and human-in-the-loop payments.
      14
      689 npm
      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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action: wallet status, quote retrieval, cross-rail comparison, payment execution, faucet claim, and swap quote. The x402_* prefix groups the payment flow while the others are clearly separate operations.

    Naming Consistency4/5

    Names are snake_case and mostly use a resource_action pattern (wallet_status, x402_pay, faucet_claim), but the x402_ prefix creates a subgroup and topup_quote is action-first. Minor inconsistency, but all are readable and predictable.

    Tool Count5/5

    Six tools is well-scoped for a nano-payment server, covering the essential operations without redundancy or bloat. Each tool earns its place.

    Completeness4/5

    The core lifecycle is covered: get funds (faucet), check balance, quote, compare rails, pay, and top-up quote. Missing direct transfer or history tools, but these are out of scope for the x402-focused design.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources