Ext Ops Panel
Open dashboard
Comparison

Stripe vs io.github.theluckystrike/duplicate-invoice-check

Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.theluckystrike/duplicate-invoice-check is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceStripeio.github.theluckystrike/duplicate-invoice-check
Docker MCP Catalog Listed
Version: sha256:92ba43f82377
Forks (GitHub): 396
Pulls (Docker Hub): 45 863
Stars (Docker Hub): 9
Stars (GitHub): 1 963
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.22.8
Forks (GitHub): 0
Stars (GitHub): 2
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 io.github.theluckystrike/duplicate-invoice-check
FactStripeio.github.theluckystrike/duplicate-invoice-check
Marketplaces that list it11
Stars (GitHub) (differs)1 963 (better)2 (worse)
Pulls (Docker Hub) (differs)45 863No figure on Docker Hub
Forks (GitHub) (differs)396 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (mcp/stripe)On your machine (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.8/duplicate-invoice-check.mcpb)
Transportstdiostdio
Tools it declares (differs)22Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/stripe/agent-toolkitgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)07
First seen (differs)2026-10-112026-10-16

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.

io.github.theluckystrike/duplicate-invoice-check

In its own words, on Official MCP Registry:

Review grouped duplicate invoice candidates from supplied records locally; no payment approval.

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)

io.github.theluckystrike/duplicate-invoice-check

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: MCP_LICENSE_KEY (secret)

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

Tools each declares

The marketplaces of io.github.theluckystrike/duplicate-invoice-check publish no list of tools, so we do not compare tools.

Settings each asks for

Only Stripe asks for

  • STRIPE_SECRET_KEY (secret)

Only io.github.theluckystrike/duplicate-invoice-check asks for

  • MCP_LICENSE_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Stripe · What it can do: io.github.theluckystrike/duplicate-invoice-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