A
licenseNot graded
qualityD
maintenanceEnables pay-per-call access control for AI agents using HTTP 402 and on-chain settlement, allowing microtransactions for API usage.
54 PyPI
MIT
@arispay/payagent-mcp
Officialby arispay-inc
Related Servers
Alternatives to @arispay/payagent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets AI agents discover, pay for, and call any HTTP API per request using USDC, with gasless nanopayments and no API keys or accounts needed.563 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to discover and pay for x402-gated HTTP APIs, handling 402 Payment Required flows with local signing. Supports EVM and Solana with non-custodial wallet management.263 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.AGPL 3.0
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.314 npmMIT
m2mcent-sdkofficial
AlicenseAqualityDmaintenanceMonetizes any API or MCP server by wrapping endpoints with the x402 payment protocol, enabling USDC micro-payments from AI agents with atomic settlement on Base L2.235 npmMIT
TDQS
A4.7/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct role: discover searches, inspect prices, pay executes, history reconciles, setup provisions, balance checks funds, and check_payment_signal buys verification evidence. Even the two pre-payment tools (inspect and check_payment_signal) are cleanly separated by cost and purpose.
Naming Consistency4/5
Most names are terse, lowercase, and command-like (discover, inspect, pay, setup), with check_payment_signal as a clear verb_noun exception. history and balance are nouns rather than list_history/get_balance, creating minor inconsistency, but the pattern remains readable and predictable.
Tool Count5/5
Seven tools is well-scoped for a payment-agent server: discovery, inspection, execution, account setup, balance lookup, history, and signal verification each earn their place. There is no bloat or sense of a thin surface.
Completeness5/5
The tool surface covers the full workflow an agent needs: discover an API, inspect its price, pay for it idempotently, check prior payments, verify resources via signal, manage account setup, and confirm balance. There are no obvious dead ends or missing critical operations for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessSlow