Ext Ops Panel
Open dashboard
Comparison

Mercado Pago vs 402xAgent

Mercado Pago is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). 402xAgent is an MCP server published by withgrokbot. 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 Pago402xAgent
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.32.2
Forks (GitHub): 0
Stars (GitHub): 1
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 402xAgent
FactMercado Pago402xAgent
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-13
Where it runs (differs)Remote server (mcp.mercadopago.com)Remote server (api.402xagent.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/withgrokbot/verified-catalog
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)Responded 2 days ago

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.

402xAgent

In its own words, on Official MCP Registry:

Check an x402 endpoint before your agent pays: pay, skip or recheck. Plus a verified x402 catalog.

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)

402xAgent As a remote MCP server

Claude Code
claude mcp add --transport http verified-catalog https://api.402xagent.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of 402xAgent responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of Mercado Pago nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of 402xAgent publish no settings it asks for, so we do not compare settings.

What it can do: Mercado Pago · What it can do: 402xAgent · 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