io.github.cyanheads/cern-opendata-mcp-server vs OpenReadout
io.github.cyanheads/cern-opendata-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). OpenReadout is an MCP server published by openreadout. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. 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 |  io.github.cyanheads/cern-opendata-mcp-server |   OpenReadout |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Downloads/month (npm): 970 Downloads/week (npm): 253 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.4.0 Downloads/month (npm): 992 Downloads/week (npm): 250 Forks (GitHub): 1 Stars (GitHub): 8 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.4.0 Downloads/month (npm): 992 Downloads/week (npm): 250 Forks (GitHub): 1 Stars (GitHub): 8 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 | io.github.cyanheads/cern-opendata-mcp-server | OpenReadout |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 8 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | 2026-10-18 (worse) | 2026-10-18 (better) |
| Where it runs (differs) | Remote server (cern-opendata.caseyjhand.com/mcp) | On your machine (openreadout) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 0 | Not published |
| Licence (differs) | Not stated | MIT OR Apache-2.0 |
| Repository (differs) | github.com/cyanheads/cern-opendata-mcp-server | github.com/openreadout/openreadout |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days 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
io.github.cyanheads/cern-opendata-mcp-server
Search CERN Open Data, fetch records, files, analysis environments, CMS good-run lists, HLT paths.
OpenReadout
Read raw lab-instrument files offline: metadata, previews, integrity checks, open-format export.
How to run each
io.github.cyanheads/cern-opendata-mcp-server As a remote MCP server
claude mcp add --transport http cern-opendata-mcp-server https://cern-opendata.caseyjhand.com/mcpOpenReadout As a local MCP server: npm package
claude mcp add --transport stdio openreadout -- npx -y openreadout mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.cyanheads/cern-opendata-mcp-server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of OpenReadout nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of OpenReadout publish no settings it asks for, so we do not compare settings.
What it can do: io.github.cyanheads/cern-opendata-mcp-server · What it can do: OpenReadout · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.