A
licenseNot graded
qualityB
maintenanceA remote MCP server enabling AI agents to accept Pix, credit/debit cards, and boleto payments in Brazil via Mercado Pago, with payment status polling and no webhooks needed.
MIT
Mercado Pago MCP Server
Officialby mercadolibre
Related Servers
Alternatives to Mercado Pago MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to accept payments in Chile using Mercado Pago, including cards, wallet, and bank transfers.MIT
- AlicenseNot gradedqualityBmaintenanceA remote MCP server that lets any AI agent accept payments in Argentina via Mercado Pago, supporting wallets, cards with cuotas, and cash.MIT
zuckpay-mcpofficial
AlicenseAqualityAmaintenanceOfficial MCP server for ZuckPay – create PIX, SPEI, and PayPal charges, and query transactions from your AI assistant.2012 npmMIT- FlicenseAqualityCmaintenanceMCP server that exposes the GestionIntegrantes REST API as tools, enabling authentication, management of personas, and user queries via natural language.10-
OrcaRail MCPofficial
AlicenseBqualityAmaintenanceOfficial MCP server for accepting crypto payments through OrcaRail. It enables AI agents to create payment intents, manage subscriptions, handle product catalogs, and get exchange rates via natural language.252 npmMIT
TDQS
B3/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as searching documentation, making it impossible to confuse with other tools.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern (search_documentation), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
Tool Count2/5
A single tool is too few for a server named 'Mercado Pago MCP Server', which implies a broader scope related to payment processing. This minimal toolset feels thin and inadequate for the apparent domain, limiting functionality to just documentation search.
Completeness1/5
The tool surface is severely incomplete for a payment processing domain. There are no tools for core operations like creating payments, checking transaction status, managing customers, or handling refunds, leaving significant gaps that will cause agent failures in typical workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues