Stripe vs 402xAgent
Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). 402xAgent is an MCP server published by withgrokbot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
| Marketplace |  Stripe |  402xAgent |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:92ba43f82377 Forks (GitHub): 364 Pulls (Docker Hub): 45 657 Stars (Docker Hub): 9 Stars (GitHub): 1 944 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.32.2 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
| Fact | Stripe | 402xAgent |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 944 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 45 657 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 364 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/stripe) | Remote server (api.402xagent.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 22 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/stripe/agent-toolkit | github.com/withgrokbot/verified-catalog |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 1 h ago |
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
Interact with Stripe services over the Stripe API.
402xAgent
Check an x402 endpoint before your agent pays: pay, skip or recheck. Plus a verified x402 catalog.
How to run each
Stripe As a local MCP server: Docker image
claude mcp add --env "STRIPE_SECRET_KEY=<YOUR_STRIPE_SECRET_KEY>" --transport stdio stripe -- docker run -i --rm -e STRIPE_SECRET_KEY mcp/stripeRequires: STRIPE_SECRET_KEY (secret)
402xAgent As a remote MCP server
claude mcp add --transport http verified-catalog https://api.402xagent.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only 402xAgent has a remote endpoint we check. How we check endpoints
Tools each declares
Only Stripe has
cancel_subscriptioncreate_couponcreate_customercreate_invoicecreate_invoice_itemcreate_payment_linkcreate_pricecreate_productcreate_refundfinalize_invoicelist_couponslist_customers
Show the remaining 10
list_disputeslist_invoiceslist_payment_intentslist_priceslist_productslist_subscriptionsretrieve_balancesearch_stripe_documentationupdate_disputeupdate_subscription
Only 402xAgent has
endpoint_spot_checkget_overnight_cos_packget_receiptget_servicelookupsearch_catalog
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (402xAgent as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of 402xAgent publish no settings it asks for, so we do not compare settings.
What it can do: Stripe · What it can do: 402xAgent · 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.