Ext Ops Panel
Open dashboard
Comparison

Mercado Pago vs io.github.krystiangw/agenticpay

Mercado Pago is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.krystiangw/agenticpay is an MCP server published by krystiangw. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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

Where each is published
MarketplaceMercado Pagoio.github.krystiangw/agenticpay
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.0.1
Downloads/month (npm): 311
Downloads/week (npm): 124
Forks (GitHub): 2
Stars (GitHub): 4
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

Mercado Pago vs io.github.krystiangw/agenticpay
FactMercado Pagoio.github.krystiangw/agenticpay
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.mercadopago.com)On your machine (@agenticpay/mcp-bridge)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 14, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/krystiangw/agenticpay
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 302 (3 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

In its own words, on Docker MCP Catalog:

Provides access to Mercado Pago Marketplace API.

io.github.krystiangw/agenticpay

In its own words, on Official MCP Registry:

x402 USDC paywall bridge for MCP — pay per tool call on Solana.

How to run each

Mercado Pago As a remote MCP server

Claude Code
claude mcp add --transport http mercado-pago https://mcp.mercadopago.com

Requires: MERCADO_PAGO_API_KEY (secret)

io.github.krystiangw/agenticpay As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTICPAY_BRIDGE_KEYPAIR=<YOUR_AGENTICPAY_BRIDGE_KEYPAIR>" --env "AGENTICPAY_BRIDGE_TOOLS=<YOUR_AGENTICPAY_BRIDGE_TOOLS>" --transport stdio agenticpay -- npx -y @agenticpay/mcp-bridge

Requires: AGENTICPAY_BRIDGE_KEYPAIR (secret), AGENTICPAY_BRIDGE_TOOLS

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.krystiangw/agenticpay asks for

  • AGENTICPAY_BRIDGE_KEYPAIR (secret)
  • AGENTICPAY_BRIDGE_NETWORK
  • AGENTICPAY_BRIDGE_RPC
  • AGENTICPAY_BRIDGE_TOOLS

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.krystiangw/agenticpay · 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.

Where the data comes from: how the catalog is built