OpenMesh vs VaultCrux Memory Core
OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). VaultCrux Memory Core is an MCP server published by CueCrux. 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: 0.2.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 | OpenMesh | VaultCrux Memory Core |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.openmesh.dev/mcp) | Remote server (api.vaultcrux.com/memory-core/mcp) |
| 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 (differs) | Not stated | github.com/cuecrux/vaultcrux |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-13 | Responded 3 days ago |
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.
VaultCrux Memory Core
VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage
How to run each
OpenMesh As a remote MCP server
claude mcp add --transport http openmesh https://api.openmesh.dev/mcpVaultCrux Memory Core As a remote MCP server
claude mcp add --transport http vaultcrux-memory-core https://api.vaultcrux.com/memory-core/mcp --header "x-api-key: <YOUR_X_API_KEY>" --header "x-tenant-id: <YOUR_X_TENANT_ID>"Requires: x-api-key header, x-tenant-id header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of VaultCrux Memory Core responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of VaultCrux Memory 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: VaultCrux Memory Core · 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.