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.
52 PyPI
MIT
@arispay/payagent-mcp
Officialby arispay-inc
Related Servers
Alternatives to @arispay/payagent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceLets AI agents discover, pay for, and call any HTTP API per request using USDC, with gasless nanopayments and no API keys or accounts needed.526 npmMIT
- AlicenseAqualityCmaintenanceEnables 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.367 npmMIT
A-Pay Protocolofficial
AlicenseBqualityBmaintenanceUniversal HTTP 402 Micropayment Protocol & Autonomous Economic Settlement Engine for AI Agents on Base L2.552 PyPIMIT- AlicenseNot gradedqualityBmaintenanceEnables 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.7AGPL 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.37 npm1MIT
TDQS
A4.4/5.0
Scored across 7 tools
Disambiguation4/5
Each tool has a distinct function: discover finds endpoints, inspect prices one, pay executes, balance locates funds, history audits past payments, check_payment_signal buys probe evidence, and setup provisions an account. The only mild overlap is between the two pre-payment diagnostics (inspect vs check_payment_signal), but the descriptions clearly separate pricing from buying evidence.
Naming Consistency3/5
Most names are single words but mix nouns (balance, history) with bare verbs (inspect, discover, pay, setup), and one tool breaks the pattern with snake_case multi-word 'check_payment_signal'. It remains readable and predictable in intent, but there is no consistent verb_noun convention.
Tool Count5/5
Seven tools is well-scoped for a payment agent, with each earning its place across the discover→inspect→pay→history→balance workflow plus account setup and a safety-verification step. No filler or redundant tools.
Completeness4/5
The surface covers the full agent-payment lifecycle: provisioning, discovery, price inspection, paying, spending audit, balance lookup, and pre-payment signal verification. Minor gaps exist (no explicit tool to modify spend mandates or manage/withdraw vIBAN funds), but core workflows are fully covered.
Maintenance
ActivityMaintained
ResponsivenessSlow