Ext Ops Panel
Open dashboard
Comparison

checkout-com-webhooks vs io.github.glongusmain/glongus-mcp

checkout-com-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.glongusmain/glongus-mcp is an MCP server published by glongusmain. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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
Marketplacecheckout-com-webhooksio.github.glongusmain/glongus-mcp
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 97
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.14.0
Downloads/month (npm): 3 139
Downloads/week (npm): 763
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.14.0
Downloads/month (npm): 3 139
Downloads/week (npm): 763
Forks (GitHub): 0
Stars (GitHub): 0
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

checkout-com-webhooks vs io.github.glongusmain/glongus-mcp
Factcheckout-com-webhooksio.github.glongusmain/glongus-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)97 (better)0 (worse)
Forks (GitHub) (differs)16 (better)0 (worse)
Last release (differs)Not published2026-10-18
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/glongusmain/glongus-mcp
Changes in the last 7 days00
First seen (differs)2026-10-212026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-25

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

checkout-com-webhooks

In its own words, on Community GitHub marketplaces:

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.

io.github.glongusmain/glongus-mcp

In its own words, on Official MCP Registry:

Let your agent buy and sell physical goods, with escrow and shipping.

How to run each

checkout-com-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install checkout-com-webhooks@webhook-skills

io.github.glongusmain/glongus-mcp As a remote MCP server

Claude Code
claude mcp add --transport http glongus-mcp https://api.glongus.com/mcp

Requires: GLONGUS_API_KEY (secret)

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

Only io.github.glongusmain/glongus-mcp 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: checkout-com-webhooks · What it can do: io.github.glongusmain/glongus-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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