OpenMesh vs org.agentmuseum/the-agent-museum
OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). org.agentmuseum/the-agent-museum is an MCP server published by agentmuseum.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  org.agentmuseum/the-agent-museum | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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 | org.agentmuseum/the-agent-museum |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.openmesh.dev/mcp) | Remote server (agentmuseum.org/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 | Not stated | Not stated |
| 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 14 h 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.
org.agentmuseum/the-agent-museum
A verifiable museum of the agent era; browse and authenticate exhibits against Bitcoin.
How to run each
OpenMesh As a remote MCP server
claude mcp add --transport http openmesh https://api.openmesh.dev/mcporg.agentmuseum/the-agent-museum As a remote MCP server
claude mcp add --transport http the-agent-museum https://agentmuseum.org/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of org.agentmuseum/the-agent-museum responded at the last daily check. How we check endpoints
Tools each declares
Only OpenMesh has
call_servicediscover_serviceget_alternativereport_experience
Only org.agentmuseum/the-agent-museum has
authenticate_exhibitget_exhibithow_to_submitlist_collectionobjects_abouton_this_daysearch_collectionthe_firststimelineunder_consideration
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (org.agentmuseum/the-agent-museum as of 2026-10-12). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: OpenMesh · What it can do: org.agentmuseum/the-agent-museum · 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.