Ext Ops Panel
Open dashboard
Comparison

chargeblast-webhooks vs ChargeGuard Dispute Assistant

chargeblast-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ChargeGuard Dispute Assistant is an MCP server published by trychargeguard.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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
Marketplacechargeblast-webhooksChargeGuard Dispute Assistant
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 101
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

chargeblast-webhooks vs ChargeGuard Dispute Assistant
Factchargeblast-webhooksChargeGuard Dispute Assistant
Marketplaces that list it11
Stars (GitHub) (differs)101No figure on GitHub
Forks (GitHub) (differs)16No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (www.trychargeguard.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/hookdeck/webhook-skillsNot stated
Changes in the last 7 days00
First seen (differs)2026-11-062026-10-28
Endpoint at the last check (differs)no remote endpoint we checkResponded 11 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

chargeblast-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Chargeblast webhooks, which are delivered by Svix. Use when setting up a Chargeblast webhook endpoint, getting the whsec_ webhook secret, debugging svix-id / svix-timestamp / svix-signature verification, or handling chargeback-prevention alert and deflection events like alert.created, alert.updated, alert.refunded, alert.will_expire and deflection.created.

ChargeGuard Dispute Assistant

In its own words, on Official MCP Registry:

Chargeback intelligence: 9 card-network reason codes, winning evidence, gateway deadlines. Free.

How to run each

chargeblast-webhooks As a Claude Code plugin

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

ChargeGuard Dispute Assistant As a remote MCP server

Claude Code
claude mcp add --transport http chargeguard https://www.trychargeguard.com/mcp

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

Only ChargeGuard Dispute Assistant 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

Neither one's marketplaces publish the settings it asks for.

What it can do: chargeblast-webhooks · What it can do: ChargeGuard Dispute Assistant · 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. 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