req-invoice-mcp
Related Servers
Alternatives to req-invoice-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables merchants to preview, create, list, and track invoices with line items, VAT, payment links, due dates, and PDFs using an assistant secret key, while ensuring payments go to the merchant's wallet and never spend funds.MIT
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- AlicenseNot gradedqualityBmaintenanceEnables AI agents to issue invoices, check invoice status, and verify invoices on NEAR testnet, with read-only operations that never sign transactions.MIT

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.210648 npmMIT
CigalPay MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to create crypto payment links priced in USD or EUR, check payment and refund status, list active payments and supported coins, and optionally issue crypto refunds.6158 npmMIT- AlicenseNot gradedqualityBmaintenanceAccept crypto payments from AI agents: create an invoice in one call and get a hosted checkout link (USDC/USDT on Celo, Base, Arbitrum, Polygon, BSC). No API key, instant self-custody settlement.MIT
TDQS
Scored across 6 tools
Each tool has a reasonably distinct role, but create_invoice and create_payment_link both 'bill someone' and could be confused at first glance, and get_payment_transactions vs check_invoice both surface payment transactions from different perspectives (payer vs payee). The descriptions do clarify these boundaries well, keeping overlap low.
All names are snake_case verb_noun, which is consistent. Minor deviation in verb choice for reads (get_payment_transactions, find_currency, check_invoice, list_invoices) rather than a single read verb, but the pattern remains predictable.
Six tools is a well-scoped surface for an invoicing server: create, pay, look up currency, check status, and list. Each tool clearly earns its place with no filler.
The core lifecycle (create invoice/link, obtain payment transactions, check paid status, list) is covered. Gaps remain around canceling/voiding an invoice, retrieving full invoice details by ID, and refunds, but agents can work around these for the primary pay-and-verify flow.