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.
55
261 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
- AlicenseBqualityCmaintenanceEnables 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.33MIT
@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.2/5.0
Scored across 93 tools
Disambiguation3/5
The domain is broad and many tools target closely related resources: payin quotes vs payout quotes vs transfer quotes vs FX quotes, and payouts split across EVM/Solana/Stellar endpoints. Descriptions clarify boundaries for expert readers, but an agent selecting from 93 OpenAPI-derived names will likely confuse overlapping quote, payout, wallet, and bank-account operations.
Naming Consistency3/5
Most tools follow an HTTP-method + versioned-path convention, so the pattern is recognizable despite being verbose and API-centric rather than action-oriented. However, there are deviations such as missing V1 segments, a typo-like PostV1EInstancesTos, and mixed semantic clarity across similar endpoints.
Tool Count1/5
93 tools is extremely large for an MCP server and far exceeds typical agent-friendly scoping. While the financial API is broad, this surface is heavy enough to cause context overload and poor tool selection.
Completeness4/5
The surface covers a wide lifecycle across customers, KYC/KYB, bank accounts, wallets, virtual accounts, blockchain wallets, payins, payouts, transfers, payables, webhooks, onboarding, RFI, yield, and available rails. There are minor gaps such as missing delete for virtual accounts and no obvious member-invite operation, but core workflows are broadly represented.
Maintenance
ActivityActive
ResponsivenessLimited data