Ext Ops Panel
Open dashboard
Comparison

Stripe vs HasData Shopify

Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). HasData Shopify is an MCP server published by hasdata.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceStripeHasData Shopify
Docker MCP Catalog Listed
Version: sha256:92ba43f82377
Forks (GitHub): 358
Pulls (Docker Hub): 45 536
Stars (Docker Hub): 9
Stars (GitHub): 1 915
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
Downloads/month (npm): 664
Downloads/week (npm): 40
Forks (GitHub): 0
Stars (GitHub): 8
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 HasData Shopify
FactStripeHasData Shopify
Marketplaces that list it11
Stars (GitHub) (differs)1 915 (better)8 (worse)
Pulls (Docker Hub) (differs)45 536No figure on Docker Hub
Forks (GitHub) (differs)358 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/stripe)Remote server (mcp.hasdata.com/mcp)
Transport (differs)stdioStreamable 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/hasdata/shopify-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 13 h ago, requires a key

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.

HasData Shopify

In its own words, on Official MCP Registry:

The public product catalogue and collections of any Shopify storefront, as structured JSON.

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)

HasData Shopify

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

Requires: HASDATA_API_KEY (secret), x-api-key header

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

Only HasData Shopify has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of HasData Shopify publish no list of tools, so we do not compare tools.

Settings each asks for

Only Stripe asks for

  • STRIPE_SECRET_KEY (secret)

Only HasData Shopify asks for

  • HASDATA_API_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: HasData Shopify · 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