Dodo Payments vs x402 Universal Payer
Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). x402 Universal Payer is an MCP server published by nirholas. 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 | ||
|---|---|---|
| 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.2 Downloads/month (npm): 167 Downloads/week (npm): 40 Forks (GitHub): 64 Stars (GitHub): 237 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 | Dodo Payments | x402 Universal Payer |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 237 |
| Forks (GitHub) (differs) | No figure on GitHub | 64 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.dodopayments.com/sse) | On your machine (@three-ws/mcp-bridge) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 13, secrets among them: 2 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/nirholas/three.ws |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago, requires a key | no 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
Tools for cross-border payments, taxes, and compliance.
x402 Universal Payer
Pay any x402 endpoint on the open web: auto-paying bridge with Bazaar discovery and spend caps.
How to run each
Dodo Payments As a remote MCP server
claude mcp add --transport sse dodo-payments https://mcp.dodopayments.com/sse
Requires: DODO_PAYMENTS_API_KEY (secret)
x402 Universal Payer As a local MCP server: npm package
claude mcp add --env "MCP_BRIDGE_EVM_PRIVATE_KEY=<YOUR_MCP_BRIDGE_EVM_PRIVATE_KEY>" --env "MCP_BRIDGE_SVM_PRIVATE_KEY=<YOUR_MCP_BRIDGE_SVM_PRIVATE_KEY>" --transport stdio x402-bridge -- npx -y @three-ws/mcp-bridge
Requires: MCP_BRIDGE_EVM_PRIVATE_KEY (secret), MCP_BRIDGE_SVM_PRIVATE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Dodo Payments has a remote endpoint we check. How we check endpoints
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 x402 Universal Payer asks for
MCP_BRIDGE_ALLOWED_HOSTSMCP_BRIDGE_ALLOWED_PAYTOMCP_BRIDGE_ALLOW_HTTPMCP_BRIDGE_BATCH_DEPOSIT_MULTIPLIERMCP_BRIDGE_BAZAAR_URLMCP_BRIDGE_DISCOVER_LIMITMCP_BRIDGE_EVM_PRIVATE_KEY (secret)MCP_BRIDGE_MAX_DEPOSIT_ATOMICMCP_BRIDGE_MAX_PRICE_PER_CALL_ATOMICMCP_BRIDGE_MAX_TOTAL_ATOMICMCP_BRIDGE_SVM_PRIVATE_KEY (secret)RPC_URL_8453
Show the remaining 1
X402_MCP_BRIDGE_CHANNELS_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Dodo Payments · What it can do: x402 Universal Payer · 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.