Stripe vs WavePay Payments
Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). WavePay Payments is an MCP server published by t3ratech. 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
| Marketplace |  Stripe | |
|---|---|---|
| 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.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
| Fact | Stripe | WavePay Payments |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 915 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 45 536 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 358 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/stripe) | Remote server (t3rnel-wavepay-production.t3ratech.workers.dev/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 | Not stated |
| 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 | not checked yet |
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.
WavePay Payments
Payments MCP: self-serve merchant key, PayNow + PayPal checkouts.
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)
WavePay Payments As a remote MCP server
claude mcp add --transport http wavepay https://t3rnel-wavepay-production.t3ratech.workers.dev/mcp --header "x-wavepay-service-key: <YOUR_X_WAVEPAY_SERVICE_KEY>"Requires: x-wavepay-service-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of WavePay Payments publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of WavePay Payments publish no settings it asks for, so we do not compare settings.
What it can do: Stripe · What it can do: WavePay Payments · 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.