Dodo Payments vs 402Signal
402Signal is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). 402Signal is an MCP server published by 402signal. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-27. 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
| Marketplace |  Dodo Payments | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Removed on 2026-10-24 Version: 0.3.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 | Dodo Payments | 402Signalno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.dodopayments.com/sse) | Remote server (402signal.com/mcp) |
| Transport (differs) | SSE | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 32 h ago, requires a key | no remote endpoint we check |
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 402Signal
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Bitcoin + Ethereum RPC for AI agents. 44 tools. x402 payments in USDC on Base mainnet.
-
Exact-amount top-two routing for six pilots; caller signs; AssetFare never signs or submits
-
Machine-native tools for autonomous agents with free routing and x402 USDC pay-per-call.
-
Let an AI agent find and pay for x402 APIs and products in USDC on Base, within owner-set limits.
-
swarm-x402-mcp io.github.swarm-agent-operator/swarm-x402-mcp
Pay-per-call x402 services from SWARM: repo scans, web research. USDC on Base.
-
70+ pay-per-call security, crypto, and data tools for AI agents via x402 USDC micropayments on Base
What each says it does
Dodo Payments
Tools for cross-border payments, taxes, and compliance.
402Signal
Fail-closed live-endpoint x402 router. POST /route, $0.01 USDC on Base, Solana, Algorand.
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)
402Signal
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
The marketplaces of 402Signal publish no settings it asks for, so we do not compare settings.
What it can do: Dodo Payments · What it can do: 402Signal · 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.