Ext Ops Panel
Open dashboard
Comparison

Mercado Pago vs McpStamp Price Catalogue

Mercado Pago is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). McpStamp Price Catalogue is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 PagoMcpStamp Price Catalogue
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.23.0
Forks (GitHub): 3
Stars (GitHub): 2
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 McpStamp Price Catalogue
FactMercado PagoMcpStamp Price Catalogue
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub3
Last release (differs)Not published2026-11-02
Where it runs (differs)Remote server (mcp.mercadopago.com)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 302 (18 h ago)Responded 21 h 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.

McpStamp Price Catalogue

In its own words, on Official MCP Registry:

A price list and labour rate card by SKU with dated prices, used to price quotes and invoices.

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)

McpStamp Price Catalogue As a remote MCP server

Claude Code
claude mcp add --transport http catalogue https://mcp.zovo.one/mcp/catalogue

Requires: MCP_LICENSE_KEY (secret)

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

Only the endpoint of McpStamp Price Catalogue responded at the last daily 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 McpStamp Price Catalogue asks for

  • MCP_LICENSE_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Mercado Pago · What it can do: McpStamp Price Catalogue · 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