Mercado Pago vs io.github.ginokino/swarmpay
Mercado Pago is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.ginokino/swarmpay is an MCP server published by ginokino. Marketplaces we read that list it: 1 (Official MCP Registry). 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.4.4 Downloads/month (PyPI): 86 Downloads/week (PyPI): 10 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 | io.github.ginokino/swarmpay |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.mercadopago.com) | On your machine (swarmpay) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 2 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/ginokino/swarmpay-sdk |
| 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.
io.github.ginokino/swarmpay
Payment layer for AI agents. Send USDC, manage escrows on Base blockchain.
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)
io.github.ginokino/swarmpay As a local MCP server: PyPI package
claude mcp add --env "CDP_API_KEY_ID=<YOUR_CDP_API_KEY_ID>" --env "CDP_API_KEY_SECRET=<YOUR_CDP_API_KEY_SECRET>" --transport stdio swarmpay -- uvx swarmpayRequires: CDP_API_KEY_ID (secret), CDP_API_KEY_SECRET (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 io.github.ginokino/swarmpay asks for
CDP_API_KEY_ID (secret)CDP_API_KEY_SECRET (secret)SWARMPAY_ADMIN_WALLETSWARMPAY_NETWORK
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Mercado Pago · What it can do: io.github.ginokino/swarmpay · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.