OpenMesh vs 402Signal
402Signal is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). 402Signal is an MCP server published by 402signalhq. 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 |  OpenMesh | |
|---|---|---|
| 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.2 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 | OpenMesh | 402Signalno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.openmesh.dev/mcp) | Remote server (402signal.com/mcp/v0.3.1) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for | Not published | 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) | Not responding since 2026-10-13 | 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.
-
Discover and call pay-per-request (x402) APIs, ranked by reliability, latency and price.
-
anchor-x402 io.github.hypeprinter007-stack/anchor-x402
x402-paid agent tools: 18 over HTTP, 14 over stdio. USDC per call, no API key.
-
GhostKey — Route Paid APIs with x402
Find paid APIs, check access policy and price, and route x402 requests. No autonomous spending.
-
AgentPay — trust routing + spend caps for x402 agents
Buyer-side trust oracle + capped sessions for x402 agents: verified_route, receipts, 17 free tools.
-
38 x402 pay-per-call tools for AI agents (USDC/USDT on Base): web, crypto, on-chain, geo, packages
-
MCP server for the @agentutility edge-market cluster — pay-per-call x402 tools, no API keys, USDC…
What each says it does
OpenMesh
Discover and connect to a curated marketplace of MCP servers for extending AI agent capabilities.
402Signal
Check paid API offers before your agent spends. Qualifying routes: $0.003 USDC. Normal misses: free.
How to run each
OpenMesh As a remote MCP server
claude mcp add --transport http openmesh https://api.openmesh.dev/mcp402Signal
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 OpenMesh has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of 402Signal publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: OpenMesh · 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.