Dodo Payments vs HPP x402 MCP Bridge
Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). HPP x402 MCP Bridge is an MCP server published by hpp-io. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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 |  Dodo Payments |   HPP x402 MCP Bridge |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.23 Downloads/month (npm): 1 441 Downloads/week (npm): 318 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.1.23 Downloads/month (npm): 1 441 Downloads/week (npm): 318 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
| Fact | Dodo Payments | HPP x402 MCP Bridge |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Remote server (mcp.dodopayments.com/sse) | On your machine (@hpp-io/x402-mcp-bridge) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 1 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | Not stated | github.com/hpp-io/x402-mcp-bridge |
| 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.
HPP x402 MCP Bridge
MCP bridge for autonomous x402 payments in HPP USDC.e — discover and pay for services per call.
How to run each
Dodo Payments As a remote MCP server
claude mcp add --transport sse dodo-payments https://mcp.dodopayments.com/sseRequires: DODO_PAYMENTS_API_KEY (secret)
HPP x402 MCP Bridge As a local MCP server: npm package
claude mcp add --env "DELEGATE_PRIVATE_KEY=<YOUR_DELEGATE_PRIVATE_KEY>" --transport stdio x402-mcp-bridge -- npx -y @hpp-io/x402-mcp-bridgeRequires: DELEGATE_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 HPP x402 MCP Bridge asks for
ALLOWANCE_MODULE_ADDRESSDELEGATE_PRIVATE_KEY (secret)HPP_NETWORKRESOURCE_SERVER_URLSAFE_ADDRESS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Dodo Payments · What it can do: HPP x402 MCP Bridge · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.