mercadopago-mcp
Related Servers
Alternatives to mercadopago-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceProvides 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- AlicenseAqualityDmaintenanceConnects AI agents to Mercado Pago, the leading payment platform in Latin America. Create payment links, search payments, get payment details, issue refunds, and retrieve merchant info.534 npm3MIT
- AlicenseBqualityCmaintenanceEnables AI agents to inspect and safely act on Paystack payments data — transactions, customers, invoices, settlements, refunds, transfers, disputes, and webhook signature checks — with read-only defaults and explicit confirmation gates before any write or money-moving call.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform PayPal payments safely through eight high-level verbs covering charges, holds, captures, voids, refunds, payouts, subscriptions, and status checks, with policy enforcement, idempotent retries, and auditable decisions.29 npmMIT

Pletopay MCP Serverofficial
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.8525 npmMIT- FlicenseNot gradedqualityBmaintenanceEnables secure, bilingual AI assistants to query and manage payments, orders, refunds, transactions, wallets, fraud risk, and statistics with per-user data isolation enforced on every tool call.-
TDQS
Scored across 6 tools
Each tool targets a distinct resource or action: single payment, merchant order, payment search, Checkout Pro preference, payment method catalog, and offline webhook signature verification. The two 'get_*' tools differ clearly by resource (payment vs merchant_order vs preference), and verify_webhook_signature is unmistakable. No two tools compete for the same request.
All names follow a clean snake_case verb_noun pattern: get_payment, get_merchant_order, search_payments, get_preference, list_payment_methods, verify_webhook_signature. Plural/singular usage matches whether the operation is a list/search versus a single fetch.
Six tools is a tight, well-scoped surface for a payments/checkout integration, with each tool earning its place. It leans slightly thin given the breadth of the Mercado Pago domain, but nothing is redundant.
The surface is read-only: it can fetch and search payments and orders and verify webhooks, but there is no create_payment, create_preference, refund_payment, or cancel operation, so agents cannot complete write-side workflows. Refund data is only visible indirectly through get_payment. These are notable gaps for a payment integration rather than minor ones.