crypto-payer-mcp
Related Servers
Alternatives to crypto-payer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA comprehensive Model Context Protocol (MCP) server for BTCPayServer integration, providing tools for payment processing, store management, user administration, webhook handling and more with full API coverage.327 npm3MIT
- AlicenseNot gradedqualityDmaintenanceA hybrid MCP server that integrates x402 payment protocol, providing tools to manage cryptocurrency payments and dynamically create HTTP endpoints protected by payments.242 npmMIT
- AlicenseAqualityCmaintenanceA local MCP server for handling X402 payment-protected HTTP endpoints, offering tools for order placement, signing, and payment submission with multiple signing modes and blockchain networks.788 npm1MIT

SnapEX Payofficial
AlicenseAqualityBmaintenanceMCP server for crypto payments: an AI agent opens its own merchant account and accepts, sends and exchanges crypto.3294 npmMIT- AlicenseAqualityDmaintenanceMCP server for ZEN.com Payment Gateway enabling payment links, transaction lookup, refunds, payouts, and reporting.1458 npmMIT
- AlicenseBqualityDmaintenanceMCP server for VNPay payment gateway (Vietnam). Supports payment URL generation, transaction queries, refunds, tokenized payments, and IPN verification with HMAC-SHA512 signing.810 npmMIT
TDQS
Scored across 6 tools
Each tool targets a distinct action: payment session creation, auth header generation, webhook signature verification, URL construction, webhook parsing, and config retrieval. Even closely related webhook tools are separated by verification versus parsing, and request_payment versus build_payment_url are clearly different stages.
All tool names follow a consistent verb_noun snake_case pattern: request_, generate_, verify_, build_, parse_, get_. There are no mixed conventions or vague verbs.
Six tools is a well-scoped set for a payment integration server. Each tool covers a distinct part of the payment flow without redundancy or bloat.
The set covers the core flow: create a payment request, build the redirect URL, generate API auth, and verify/parse incoming webhooks. A notable gap is the lack of a direct payment-status lookup or cancellation/refund operation, though webhooks may partially cover status delivery.