Stripe vs io.github.ByteBunny-io/nanocart-mcp
Stripe is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑25.
Stripe is an MCP server published by stripe. No marketplace we read lists it any more. io.github.ByteBunny-io/nanocart-mcp is an MCP server published by ByteBunny-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Removed on 2026-10-25 Version: sha256:92ba43f82377 Forks (GitHub): 375 Pulls (Docker Hub): 46 089 Stars (Docker Hub): 9 Stars (GitHub): 1 965 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 Downloads/month (npm): 192 Downloads/week (npm): 22 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | Stripeno longer listed · | io.github.ByteBunny-io/nanocart-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 965 | 0 |
| Pulls (Docker Hub) (differs) | 46 089 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 375 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/stripe) | Remote server (mcp.nanocart.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 22 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/stripe/agent-toolkit | github.com/bytebunny-io/nanocart-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Stripe
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
stripe-billing io.github.theluckystrike/stripe-billing
Read your Stripe billing data from AI chat: balances, invoices, subscriptions. Read-only.
-
Develop your payments integration faster with the ability to create products, prices, and payment links directly in ChatGPT. Run your business from ChatGPT with the ability to…
-
Read-only MCP server for querying Stripe customers, payments, and invoices.
-
mcp-stripe io.github.infoinlet-marketplace/mcp-stripe
Read-only Stripe for AI agents — customers, charges, subscriptions, invoices, balance.
-
Query and manage Paddle Billing: pricing, subscriptions, payments, revenue reports and webhooks.
-
mcp com.stripe/mcp
MCP server integrating with Stripe - tools for customers, products, payments, and more.
What each says it does
Stripe
Interact with Stripe services over the Stripe API.
io.github.ByteBunny-io/nanocart-mcp
Manage your NanoCart store from any AI agent: products, orders, coupons, subscribers, reports.
How to run each
Stripe
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.ByteBunny-io/nanocart-mcp As a remote MCP server
claude mcp add --transport http nanocart-mcp https://mcp.nanocart.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: NANOCART_API_KEY (secret), NANOCART_STORE_ID, Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.ByteBunny-io/nanocart-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.ByteBunny-io/nanocart-mcp 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.ByteBunny-io/nanocart-mcp asks for
NANOCART_API_KEY (secret)NANOCART_STORE_ID
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.ByteBunny-io/nanocart-mcp · 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.