paybond-mcp-Python
Related Servers
Alternatives to paybond-mcp-Python
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables an AI agent to settle HTTP 402-gated resources end-to-end: quote conversions, choose from the seller's accepted rails, sign gasless EIP-712 authorizations under enforced per-call and lifetime caps, and verify settlement receipts while tracking wallet balance. Runs self-hosted over stdio or Streamable HTTP, defaulting to testnet with mainnet requiring explicit confirmation.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to integrate stablecoin crypto checkout into applications by registering workspaces, configuring settlement wallets and webhooks, creating payment links and invoices, and verifying payment status and webhook signatures. It exposes these payment operations as tools over stdio so agents can complete end-to-end payment setup without manual dashboard work.-

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- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to integrate stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based entitlement logic into applications.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to integrate stablecoin crypto checkout, payment links, payment status checks, webhook verification, and webhook-based access logic into applications.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
TDQS
Scored across 31 tools
Each tool has a meticulously crafted description that clearly states its purpose and explicitly lists what NOT to use it for, eliminating ambiguity even across similar-looking tools like paybond_create_intent vs paybond_create_spend_intent.
All tools follow a consistent 'paybond_verb_noun' pattern (e.g., get, verify, submit, list, create) with optional version suffixes, making the naming predictable and systematic.
With 31 tools, the server is far beyond the typical 3-15 range. While the domain is complex, the large surface area can overwhelm agents and increase selection difficulty.
The tool set covers a broad range of fintech operations: identity, intents, capabilities, evidence, fraud, reputation, A2A, receipts, and mandates. Minor gaps like refunds or dispute resolution might exist, but core workflows are well-supported.