Ext Ops Panel
Open dashboard
Comparison

Stripe vs Xavio Merchant

Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). Xavio Merchant is an MCP server published by xavio.in. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
MarketplaceStripeXavio Merchant
Docker MCP Catalog Listed
Version: sha256:92ba43f82377
Forks (GitHub): 381
Pulls (Docker Hub): 46 405
Stars (Docker Hub): 9
Stars (GitHub): 1 976
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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 Xavio Merchant
FactStripeXavio Merchant
Marketplaces that list it11
Stars (GitHub) (differs)1 976No figure on GitHub
Pulls (Docker Hub) (differs)46 405No figure on Docker Hub
Forks (GitHub) (differs)381No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/stripe)Remote server (xavio.in/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)22Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/stripe/agent-toolkitNot stated
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days 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

In its own words, on Docker MCP Catalog:

Interact with Stripe services over the Stripe API.

Xavio Merchant

In its own words, on Official MCP Registry:

Authenticated MCP for Xavio merchants: stories, products, schedules.

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)

Xavio Merchant As a remote MCP server

Claude Code
claude mcp add --transport http merchant https://xavio.in/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Xavio Merchant has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Xavio Merchant publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Xavio Merchant publish no settings it asks for, so we do not compare settings.

What it can do: Stripe · What it can do: Xavio Merchant · 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