Context7 vs Medical Terminologies MCP
Context7 is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Medical Terminologies MCP is an MCP server published by SidneyBissoli. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.4.0 Downloads/month (npm): 3 707 Downloads/week (npm): 246 Forks (GitHub): 6 Stars (GitHub): 16 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.4.0 Downloads/month (npm): 3 707 Downloads/week (npm): 246 Forks (GitHub): 6 Stars (GitHub): 16 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 | Context7 | Medical Terminologies MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 16 |
| Forks (GitHub) (differs) | No figure on GitHub | 6 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Remote server (mcp.context7.com/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/sidneybissoli/medical-terminologies-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | Responded 25 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
Context7
Pull up-to-date, version-specific documentation and code examples for any library or framework straight into your prompt.
Medical Terminologies MCP
Diagnoses, drugs & lab codes: ICD-11, LOINC, RxNorm, MeSH, ATC, CID-10. 33 tools, MIT.
How to run each
Context7 As a remote MCP server
claude mcp add --transport http context7 https://mcp.context7.com/mcp
Requires: CONTEXT7_API_KEY (secret)
Medical Terminologies MCP As a remote MCP server
claude mcp add --transport http medical-terminologies-mcp https://medical.sidneybissoli.com/mcp
Requires: WHO_CLIENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of Context7 nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only Context7 asks for
CONTEXT7_API_KEY (secret)
Only Medical Terminologies MCP asks for
LOG_LEVELWHO_CLIENT_IDWHO_CLIENT_SECRET (secret)WHO_ICD11_RELEASE_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Context7 · What it can do: Medical Terminologies 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 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.