Ext Ops Panel
Open dashboard
Comparison

Stripe vs Alternative Payments

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. Alternative Payments is an MCP server published by wyre-technology. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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

Where each is published
MarketplaceStripeAlternative Payments
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.0.8
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

Stripe vs Alternative Payments
FactStripeno longer listed · Alternative Payments
Marketplaces that list it (differs)01
Stars (GitHub) (differs)1 9650
Pulls (Docker Hub) (differs)46 089No figure on Docker Hub
Forks (GitHub) (differs)3750
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/stripe)On your machine (ghcr.io/wyre-technology/alternative-payments-mcp:v1.0.8)
Transportstdiostdio
Tools it declares (differs)22Not published
Environment variables it asks for (differs)1, secrets among them: 16, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/stripe/agent-toolkitgithub.com/wyre-technology/alternative-payments-mcp
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

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.

    by theluckystrike · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Stripe

    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…

    by Stripe · Plugin bundle

    Listed on: Codex: openai-curated (openai/plugins) · Describes nearly the same job

  • Stripe MCP

    Read-only MCP server for querying Stripe customers, payments, and invoices.

    by robinafaruqia · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • mcp-stripe io.github.infoinlet-marketplace/mcp-stripe

    Read-only Stripe for AI agents — customers, charges, subscriptions, invoices, balance.

    by infoinlet-marketplace · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Paddle

    Query and manage Paddle Billing: pricing, subscriptions, payments, revenue reports and webhooks.

    by paddle.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • mcp com.stripe/mcp

    MCP server integrating with Stripe - tools for customers, products, payments, and more.

    by stripe.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Stripe

In its own words, on Docker MCP Catalog:

Interact with Stripe services over the Stripe API.

Alternative Payments

In its own words, on Official MCP Registry:

MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.

How to run each

Stripe

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Alternative Payments As a local MCP server: Docker image

Claude Code
claude mcp add --env "ALTERNATIVE_PAYMENTS_CLIENT_ID=<YOUR_ALTERNATIVE_PAYMENTS_CLIENT_ID>" --env "ALTERNATIVE_PAYMENTS_CLIENT_SECRET=<YOUR_ALTERNATIVE_PAYMENTS_CLIENT_SECRET>" --transport stdio alternative-payments-mcp -- docker run -i --rm -e ALTERNATIVE_PAYMENTS_CLIENT_ID -e ALTERNATIVE_PAYMENTS_CLIENT_SECRET ghcr.io/wyre-technology/alternative-payments-mcp:v1.0.8

Requires: ALTERNATIVE_PAYMENTS_CLIENT_ID (secret), ALTERNATIVE_PAYMENTS_CLIENT_SECRET (secret)

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

Tools each declares

The marketplaces of Alternative Payments publish no list of tools, so we do not compare tools.

Settings each asks for

Only Stripe asks for

  • STRIPE_SECRET_KEY (secret)

Only Alternative Payments asks for

  • ALTERNATIVE_PAYMENTS_CLIENT_ID (secret)
  • ALTERNATIVE_PAYMENTS_CLIENT_SECRET (secret)
  • ALTERNATIVE_PAYMENTS_ENVIRONMENT
  • AUTH_MODE
  • LOG_LEVEL
  • MCP_TRANSPORT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Stripe · What it can do: Alternative 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.

Where the data comes from: how the catalog is built