Ext Ops Panel
Open dashboard
Comparison

Stripe vs io.github.theluckystrike/aging

Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.theluckystrike/aging 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-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
MarketplaceStripeio.github.theluckystrike/aging
Docker MCP Catalog Listed
Version: sha256:92ba43f82377
Forks (GitHub): 360
Pulls (Docker Hub): 45 589
Stars (Docker Hub): 9
Stars (GitHub): 1 935
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.22.5
Forks (GitHub): 0
Stars (GitHub): 1
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/aging
FactStripeio.github.theluckystrike/aging
Marketplaces that list it11
Stars (GitHub) (differs)1 935 (better)1 (worse)
Pulls (Docker Hub) (differs)45 589No figure on Docker Hub
Forks (GitHub) (differs)360 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/stripe)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
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)08
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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/aging

In its own words, on Official MCP Registry:

Age your receivables into 0-30, 31-60, 61-90 and over 90 day buckets by due date.

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/aging As a remote MCP server

Claude Code
claude mcp add --transport http statement-of-account https://mcp.zovo.one/mcp/statement-of-account --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: MCP_LICENSE_KEY (secret), Authorization header

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/aging 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/aging 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/aging · 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