Ext Ops Panel
Open dashboard
Comparison

Dodo Payments vs Orbis API Marketplace

Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Orbis API Marketplace is an MCP server published by OrbisAPI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceDodo PaymentsOrbis API Marketplace
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.7
Forks (GitHub): 0
Stars (GitHub): 2
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

Dodo Payments vs Orbis API Marketplace
FactDodo PaymentsOrbis API Marketplace
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.dodopayments.com/sse)On your machine (@orbisapi/mcp)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/orbisapi/orbis-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Dodo Payments

In its own words, on Docker MCP Catalog:

Tools for cross-border payments, taxes, and compliance.

Orbis API Marketplace

In its own words, on Official MCP Registry:

8,000+ pay-per-call APIs via x402 USDC micropayments on Base. No API keys needed.

How to run each

Dodo Payments

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

Requires: DODO_PAYMENTS_API_KEY (secret)

Orbis API Marketplace As a local MCP server: npm package

Claude Code
claude mcp add --env "WALLET_PRIVATE_KEY=<YOUR_WALLET_PRIVATE_KEY>" --transport stdio orbis-mcp -- npx -y @orbisapi/mcp

Requires: WALLET_PRIVATE_KEY (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Dodo Payments asks for

  • DODO_PAYMENTS_API_KEY (secret)

Only Orbis API Marketplace asks for

  • WALLET_PRIVATE_KEY (secret)

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

What it can do: Dodo Payments · What it can do: Orbis API Marketplace · 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