CigalPay MCP Server
OfficialRelated Servers
Alternatives to CigalPay MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables an AI coding assistant to create and manage products, prices, payment links, invoices, customers, subscriptions, entitlements, refunds, and webhooks, simulate test payments, read payments and receipts, and verify buyer access through a crypto payment API.38532 npmMIT

MercanPay MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to create, look up, list, and cancel crypto invoices, manage reusable payment links, check USDT and TRX rates, and simulate test payments through a secure API.7MIT
cryptunnel-mcpofficial
AlicenseAqualityCmaintenanceEnables coding agents to create and look up crypto payments over stdio, returning checkout links, payment statuses, paged payment lists, and receivable currencies, with real payments gated behind an explicit opt-in environment flag.4MIT- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to set up crypto checkout integration by registering workspaces, creating paylinks and public payment invoices, configuring webhook endpoints, verifying webhook signatures, and checking stablecoin payment status.-

stablevoy-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to create USDT and USDC invoices, retrieve payment links, and check invoice and store payment status across connected payment-gateway stores via the Model Context Protocol.2101,449 npmMIT- 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
TDQS
Scored across 6 tools
Each tool has a distinct action scope: create, single-payment lookup by id, lookups by order reference, coin listing, pending listing, and refund listing. The three payment-reading tools (get_payment, get_payments_by_order, list_active_payments) are close in purpose, but the descriptions make the lookup key explicit enough that an agent can pick correctly.
All six tools follow a strict snake_case verb_noun pattern (create_checkout, get_payment, list_supported_coins, etc.) with consistent use of get_ for single lookups and list_ for collections. The only minor quirk is create_checkout naming the outcome 'checkout' rather than 'payment', which is still predictable and readable.
Six tools is tightly scoped to the payment-gateway domain: one create path, three read paths, and two reference-data/list tools. Nothing feels redundant or padded.
Core flow (create checkout, check status, track by order, list pending, list coins) is covered, but there is no way to create or cancel a refund or cancel a payment—only list_refunds exists. These are notable lifecycle gaps that would force an agent to fall back to the web dashboard.