Ext Ops Panel
Open dashboard
Comparison

Stripe vs Counterparty Check

Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). Counterparty Check is an MCP server published by chtwebllc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-06. 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
MarketplaceStripeCounterparty Check
Docker MCP Catalog Listed
Version: sha256:92ba43f82377
Forks (GitHub): 384
Pulls (Docker Hub): 46 920
Stars (Docker Hub): 9
Stars (GitHub): 2 043
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

Stripe vs Counterparty Check
FactStripeCounterparty Check
Marketplaces that list it11
Stars (GitHub) (differs)2 043No figure on GitHub
Pulls (Docker Hub) (differs)46 920No figure on Docker Hub
Forks (GitHub) (differs)384No figure on GitHub
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (mcp/stripe)Remote server (counterpartycheck.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)22Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/stripe/agent-toolkitNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 32 h ago returned HTTP 405

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.

Counterparty Check

In its own words, on Official MCP Registry:

Check a payee before your agent pays: sanctions, lookalike domains, payment details, invoice fraud.

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)

Counterparty Check As a remote MCP server

Claude Code
claude mcp add --transport http counterparty-check https://counterpartycheck.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Counterparty Check has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Counterparty Check publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Counterparty Check publish no settings it asks for, so we do not compare settings.

What it can do: Stripe · What it can do: Counterparty Check · 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