Mercado Pago vs checkout-com-webhooks
Mercado Pago is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). checkout-com-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Community marketplace hookdeck/webhook-skills | Not listed | Listed Version: not stated Forks (GitHub): 16 Stars (GitHub): 92 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 | checkout-com-webhooks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 92 |
| Forks (GitHub) (differs) | No figure on GitHub | 16 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.mercadopago.com) | Installs as a plugin bundle |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/hookdeck/webhook-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
| Endpoint at the last check (differs) | Answered with HTTP 302 (9 h 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.
checkout-com-webhooks
Receive and verify Checkout.com webhooks (checkout.com — the global payments processor: card acquiring, APMs, disputes, payouts, issuing). Use when setting up a Checkout.com webhook handler, debugging Cko-Signature verification, or handling events like payment_approved, payment_captured, payment_declined, payment_refunded, dispute_received or fraud_reported. Checkout.com signs with HMAC-SHA256 over the RAW body, hex-encoded, in the Cko-Signature header, and can optionally send a static Authorization header key. Not Checkout Page (checkoutpage.com), not CheckoutJoy, not 2Checkout / Verifone, not Stripe Checkout, not Shopify checkout webhooks.
How to run each
Mercado Pago As a remote MCP server
claude mcp add --transport http mercado-pago https://mcp.mercadopago.com
Requires: MERCADO_PAGO_API_KEY (secret)
checkout-com-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install checkout-com-webhooks@webhook-skills
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
The marketplaces of checkout-com-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: Mercado Pago · What it can do: checkout-com-webhooks · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.