OpenMesh vs @mcpfusion/core
OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). @mcpfusion/core is an MCP server published by @mcpfusion. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |  OpenMesh | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 5.1.0 Downloads/month (npm): 4 777 Downloads/week (npm): 854 Forks (GitHub): 24 Stars (GitHub): 255 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 | @mcpfusion/core |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 255 |
| Forks (GitHub) (differs) | No figure on GitHub | 24 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.openmesh.dev/mcp) | On your machine (@mcpfusion/core) |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | Not stated | github.com/vinkius-labs/mcpfusion |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | No HTTP response at the last check (4 h ago) | 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
OpenMesh
Discover and connect to a curated marketplace of MCP servers for extending AI agent capabilities.
@mcpfusion/core
MVA (Model-View-Agent) framework for the Model Context Protocol. Structured perception packages with Presenters, cognitive guardrails, self-healing errors, action consolidation, and tRPC-style type safety — so AI agents perceive and act on your data det
How to run each
OpenMesh As a remote MCP server
claude mcp add --transport http openmesh https://api.openmesh.dev/mcp@mcpfusion/core
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 @mcpfusion/core 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: @mcpfusion/core · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.