nano-pay
Related Servers
Alternatives to nano-pay
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityFmaintenanceCombines wallets, onramps, and payments via x402 to enable AI agents to autonomously discover and pay for services without API keys or complex setup.4258Apache 2.0- AlicenseAqualityAmaintenanceA 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.89MIT
- AlicenseNot gradedqualityBmaintenanceNon-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.31Business Source 1.1
- AlicenseAqualityBmaintenanceL402 + 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.11340MIT

token4u-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to call LLM APIs via x402 micropayments in USDC on Base network, manage a local wallet, and query consumption records.318MIT
PayAgents MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to autonomously make policy-controlled payments for APIs and tools via Bitcoin Lightning (L402) and Base USDC (x402), including paying paywalled endpoints, checking balances, and reviewing transactions.391MIT
TDQS
Scored across 6 tools
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.
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.
Six tools is well-scoped for a nano-payment server, covering the essential operations without redundancy or bloat. Each tool earns its place.
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.