khqrpay-mcp
Related Servers
Alternatives to khqrpay-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityCmaintenanceEnables AI agents to manage payments, virtual accounts, customers, transfers, refunds, settlements, checkout, payment links, invoices, subscriptions, reports, webhooks, and sandbox operations through the API, with built-in safeguards for live money movement.8576 npmMIT
Alternative Payments MCPofficial
AlicenseNot gradedqualityCmaintenanceProvides AI assistants with read and safe-write access to Alternative Payments customers, invoices, payment requests, transactions, payouts, and webhooks without directly moving money.Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to interact with MonCashConnect payment data read-only, including checking balances, listing transactions, and viewing payment details, without moving money.5 npmMIT
- AlicenseAqualityBmaintenanceEnables code agents to search platform documentation and perform permitted API operations using their own keys, defaulting to QA. It supports read-only account data and payment-link creation or cancellation while excluding administrative, credential, webhook, and money-moving operations.352 npmMIT

Tegro.money MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to create payment links, invoices, and read order/balance status for Tegro.money payment shops, with safe read-and-collect-only access.610 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect BLMPay balances, payments, payouts, webhooks, and API capabilities through MCP tools, with write/financial tools disabled by default for security.MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: usage/limits (get_usage), creation (create_test_payment), state transition (simulate_test_payment), single read (get_payment), bulk read (list_payments), and webhook verification (check_webhook_signature). The only near-neighbors, get_payment vs list_payments and create_test_payment vs simulate_test_payment, are explicitly differentiated by 'one payment' vs 'one page' and 'create' vs 'move' language.
All six tools follow a uniform snake_case verb_noun pattern (get_, create_, simulate_, list_, check_). The shared test_payment suffix groups related tools rather than creating inconsistency.
Six tools is well-scoped for a test-only payment API: usage, create, simulate, get, list, and signature check each cover a distinct step with no filler. Nothing feels padded or missing at the count level.
The test-payment lifecycle is closed: create -> simulate (including expired-then-paid for late payments) -> get/list -> verify webhook signature, plus account usage. Minor gaps remain: no refund/cancel operation, no webhook endpoint registration or event listing, and live payments are excluded by design.