OpenMesh vs AlphaFold Sovereign MCP
OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). AlphaFold Sovereign MCP is an MCP server published by smaniches. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-30. 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 |  AlphaFold Sovereign MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.9 Downloads/month (PyPI): 745 Downloads/week (PyPI): 534 Forks (GitHub): 2 Stars (GitHub): 4 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.5.7 Downloads/month (PyPI): 745 Downloads/week (PyPI): 534 Forks (GitHub): 2 Stars (GitHub): 4 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 | AlphaFold Sovereign MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 4 |
| Forks (GitHub) (differs) | No figure on GitHub | 2 |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | Remote server (api.openmesh.dev/mcp) | On your machine (alphafold-sovereign-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/smaniches/alphafold-sovereign-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| 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. 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.
AlphaFold Sovereign MCP
MCP server for AlphaFold and 8 other biomedical data sources with a local SQLite knowledge graph
How to run each
OpenMesh As a remote MCP server
claude mcp add --transport http openmesh https://api.openmesh.dev/mcpAlphaFold Sovereign MCP As a local MCP server: PyPI package
claude mcp add --transport stdio alphafold-sovereign-mcp -- uvx alphafold-sovereign-mcpCommands 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 AlphaFold Sovereign MCP 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: AlphaFold Sovereign MCP · 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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.