XPayr MCP Server
OfficialRelated Servers
Alternatives to XPayr MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI agents to accept non-custodial crypto payments by creating hosted checkout sessions and invoices, tracking payments and wallets, registering and verifying signed webhooks, purchasing prepaid credits, and querying or exporting the book of record. Test-mode payment simulation lets agents verify the full flow end to end.MIT- AlicenseNot gradedqualityCmaintenanceAccept crypto payments from AI agents: create an invoice in one call and get a hosted checkout link (USDC/USDT on Celo, Base, Arbitrum, Polygon, BSC). No API key, instant self-custody settlement.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and MCP hosts to register payment workspaces, create stablecoin paylinks, configure webhooks, verify payment signatures, and check payment status so applications can add hosted crypto checkout and webhook-based entitlements without manual dashboard setup.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents and MCP hosts to register a workspace, create stablecoin checkout and payment links, configure webhooks, verify crypto payment status, and add webhook-based access logic to applications.-
- FlicenseNot gradedqualityAmaintenanceLets AI coding agents integrate crypto checkout, payment links, payment status checks, and webhook-based entitlements into applications.-

PayRam MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceEnables AI agents to deploy and operate a self-hosted, no-signup crypto payment gateway with multi-chain support, card-to-crypto checkout, and MCP tools for payment links and integration snippets.158-
TDQS
Scored across 21 tools
Most tools target a distinct resource+action (sessions, AI agents, intents, webhooks, merchant, networks). The main soft spots are get_payment_session vs get_public_payment_status (both return session status/tx_hash, distinguished only by auth/polling context) and approve_agent_intent's optional 'bridge to checkout' behavior that overlaps with bridge_agent_intent_to_checkout.
All 21 tools use the same xpayr_ prefix plus snake_case verb_noun naming (create_payment_session, list_ai_agents, update_ai_agent_policy, reject_agent_intent). The only deviation is the noun-first xpayr_health_check, which is a trivial and conventional exception.
21 tools is on the heavy side but the server legitimately spans several sub-domains: payment sessions, AI agent commerce, webhooks, merchant account, and fee calculation. Each tool maps to an identifiable operation, though a few (coupon apply, fee calculator) could arguably be folded into broader session tools.
Core lifecycles are well covered: session create/get/list plus coupon and public status, full agent intent flow (submit, list, approve, reject, bridge), and webhook configure/test. Gaps exist around session cancellation/expiry management, coupon admin, and agent deletion/credential revocation, but these are workaround-able for the main payment flow.