Stripe vs Yolfi Payments MCP
Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). Yolfi Payments MCP is an MCP server published by yolfinance. 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 |  Yolfi Payments MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:92ba43f82377 Forks (GitHub): 370 Pulls (Docker Hub): 45 677 Stars (Docker Hub): 9 Stars (GitHub): 1 952 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 281 Downloads/week (npm): 36 Forks (GitHub): 1 Stars (GitHub): 178 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 | Yolfi Payments MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 952 (better) | 178 (worse) |
| Pulls (Docker Hub) (differs) | 45 677 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 370 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/stripe) | Remote server (app.yolfi.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 | 2, secrets among them: 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/stripe/agent-toolkit | github.com/yolfinance/yolfi-agent |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 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
Interact with Stripe services over the Stripe API.
Yolfi Payments MCP
Let AI agents add Yolfi crypto checkout, paylinks, webhooks, and status checks.
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)
Yolfi Payments MCP As a remote MCP server
claude mcp add --transport http yolfi-agent https://app.yolfi.com/mcpRequires: YOLFI_API_KEY (secret), YOLFI_WEBHOOK_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Yolfi Payments MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Yolfi Payments 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 Yolfi Payments MCP asks for
YOLFI_API_KEY (secret)YOLFI_WEBHOOK_SECRET (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Stripe · What it can do: Yolfi Payments 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.