Mercado Pago vs Decionis Commerce Gate MCP
Mercado Pago is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Decionis Commerce Gate MCP is an MCP server published by decionis.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Mercado Pago | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 802 Downloads/week (npm): 157 Forks (GitHub): 59 Stars (GitHub): 688 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 802 Downloads/week (npm): 157 Forks (GitHub): 59 (last published figure) Stars (GitHub): 688 (last published figure) Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Mercado Pago | Decionis Commerce Gate MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 688 |
| Forks (GitHub) (differs) | No figure on GitHub | 59 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (mcp.mercadopago.com) | On your machine (@decionis/commerce) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 1 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | Not stated | github.com/decionis/commerce |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 302 (5 days ago) | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Mercado Pago
Provides access to Mercado Pago Marketplace API.
Decionis Commerce Gate MCP
Commerce preflights, agent run mandates, D365 authorization, and offer checks; no external writes.
How to run each
Mercado Pago As a remote MCP server
claude mcp add --transport http mercado-pago https://mcp.mercadopago.comRequires: MERCADO_PAGO_API_KEY (secret)
Decionis Commerce Gate MCP As a local MCP server: npm package
claude mcp add --env "DECIONIS_API_KEY=<YOUR_DECIONIS_API_KEY>" --transport stdio commerce-gate -- npx -y @decionis/commerceRequires: DECIONIS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Mercado Pago has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Mercado Pago asks for
MERCADO_PAGO_API_KEY (secret)
Only Decionis Commerce Gate MCP asks for
AGENTOPS_AUTO_PROVISIONAGENTOPS_HOMEDECIONIS_API_BASEDECIONIS_API_KEY (secret)DECIONIS_ORG_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Mercado Pago · What it can do: Decionis Commerce Gate MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.