Ext Ops Panel
Open dashboard
Comparison

Stripe vs tokenio-webhooks

Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). tokenio-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

Where each is published
MarketplaceStripetokenio-webhooks
Docker MCP Catalog Listed
Version: sha256:92ba43f82377
Forks (GitHub): 380
Pulls (Docker Hub): 45 897
Stars (Docker Hub): 9
Stars (GitHub): 1 964
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

Stripe vs tokenio-webhooks
FactStripetokenio-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)1 964 (better)92 (worse)
Pulls (Docker Hub) (differs)45 897No figure on Docker Hub
Forks (GitHub) (differs)380 (better)16 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/stripe)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)22Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceMITMIT
Repository (differs)github.com/stripe/agent-toolkitgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21

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

Stripe

In its own words, on Docker MCP Catalog:

Interact with Stripe services over the Stripe API.

tokenio-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Token.io webhooks. Use when setting up Token.io webhook handlers, debugging Ed25519 signature verification, subscribing to webhook config via PUT /webhook/config, or handling open banking / A2A payment events like PAYMENT_STATUS_CHANGED, REFUND_STATUS_CHANGED, VRP_STATUS_CHANGED, and VIRTUAL_ACCOUNT_CREDIT_RECEIVED. Note: Token.io does NOT use HMAC or Standard Webhooks — it signs the raw body with an ASYMMETRIC Ed25519 signature in the token-signature header, verified with your member's Ed25519 public key.

How to run each

Stripe As a local MCP server: Docker image

Claude Code
claude mcp add --env "STRIPE_SECRET_KEY=<YOUR_STRIPE_SECRET_KEY>" --transport stdio stripe -- docker run -i --rm -e STRIPE_SECRET_KEY mcp/stripe

Requires: STRIPE_SECRET_KEY (secret)

tokenio-webhooks As a Claude Code plugin

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

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

Tools each declares

The marketplaces of tokenio-webhooks publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of tokenio-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: Stripe · What it can do: tokenio-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.

Where the data comes from: how the catalog is built