@arispay/payagent-mcpofficial
A
licenseA
qualityA
maintenanceEnables AI agents to call paid APIs and settle HTTP 402 payment challenges with USDC on Base, without private keys ever being involved.
7
168 npm
MIT
CryptoAPIs x402 Pay MCP
OfficialRelated Servers
Alternatives to CryptoAPIs x402 Pay MCP
No user-submitted related servers found.
Related Servers
- 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 gradedqualityAmaintenanceEnables AI agents to discover, call, and pay for existing HTTP APIs over MCP with x402 paywalls, non-custodial settlement, and no code changes to the backend.171 npm30Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables pay-per-call access control for AI agents using HTTP 402 and on-chain settlement, allowing microtransactions for API usage.43 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to make payments over x402-priced HTTP APIs using USDC on Monad testnet, with policy enforcement, budgets, and approval workflows, without exposing private keys.4AGPL 3.0
@hpp-io/x402-mcp-bridgeofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously pay for and discover services using HPP USDC.e over the x402 protocol, without API keys or manual signing.54 npmApache 2.0
TDQS
A4.6/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: x402_pay for HTTP URLs, x402_pay_tool for paid MCP tools on other servers, and x402_discover for finding paid endpoints. The descriptions explicitly cross-reference each other ('use x402_pay for an HTTP url, and THIS for a paid tool') to eliminate misselection.
Naming Consistency4/5
All three share a consistent x402_ prefix and snake_case style, which is highly predictable. The only minor deviation is that pay_tool adds a qualifier rather than following a strict verb_noun pattern like the other two, but overall naming is coherent.
Tool Count4/5
Three tools is on the lean side but each earns its place in a narrowly scoped payment domain. The surface is well-scoped with no redundancy, though a small set of supporting tools (e.g. balance/status) could round it out.
Completeness4/5
Core payment lifecycle is covered: discovery, HTTP payment, and MCP-tool payment, with settlement receipts returned. Minor gaps exist around checking wallet balance, payment history, or supported-network queries, which agents can work around but would strengthen the surface.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive