Stables MCP Serverofficial
A
licenseB
qualityB
maintenanceEnables AI agents to manage stablecoin payments including customer management, quotes, transfers, virtual accounts, and webhooks via the Stables API.
51
212 npm
MIT
BlindPay MCP Server
by blindpaylabs
Related Servers
Alternatives to BlindPay MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, create payment links and invoices, configure webhooks, verify payment signatures, and gate access based on confirmed payment events.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage TheyPaid accounts, stores, connected wallets, and service credits, and to create invoices or payment links and monitor payment status through natural-language workflows.MIT
@payre/mcpofficial
AlicenseAqualityCmaintenanceEnables AI assistants to securely interact with Payre's Web3 payment gateway for generating crypto checkout invoices, monitoring settlements, managing payout destinations, and inspecting analytics.18MIT- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based entitlement logic to applications. It also provides tools for workspace registration, settlement and webhook configuration, paylink creation, and crypto payment status checks.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, payment links, status checks, and verified webhook-based entitlements to applications.MIT
TDQS
C2.3/5.0
Scored across 92 tools
Disambiguation3/5
The tools mostly map to distinct REST endpoints, and detailed descriptions help distinguish resources and actions. However, the set has many closely related variants such as payin/payout/transfer quotes, payin/payout execution endpoints across EVM/Solana/Stellar, and multiple wallet and bank-account subtypes, creating real selection ambiguity at scale.
Naming Consistency4/5
Names consistently follow an HTTP-method plus API-path convention, e.g. GetV1InstancesCustomers, PostV1InstancesPayinsEvm, DeleteV1InstancesWebhookEndpointsById. There are minor inconsistencies such as the odd `PostV1EInstancesTos` and `GetInstancesCustomersBankAccountsOfframpWalletsById` missing `V1`, but the overall pattern is predictable.
Tool Count1/5
92 tools is an extreme surface for an MCP server and far exceeds the typical 3-15 range. While the domain is broad, exposing nearly every REST endpoint as a separate tool makes discovery and correct selection unnecessarily difficult.
Completeness4/5
The surface covers the payment lifecycle broadly: customers, KYC/KYB, bank accounts, wallets, virtual accounts, payins, payouts, quotes, transfers, payables, webhooks, fees, onboarding, and compliance documents. There are minor gaps such as limited update/delete coverage for immutable payment objects, but no major dead ends for core workflows.
Maintenance
ActivityActive
ResponsivenessUnresponsive