io.github.cyanheads/pubmed-mcp-server vs PatentRef
io.github.cyanheads/pubmed-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). PatentRef is an MCP server published by patentref. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2.12.0 Downloads/month (npm): 16 172 Downloads/week (npm): 3 393 Forks (GitHub): 25 Stars (GitHub): 167 Not marked · First seen |
Listed Version: 0.4.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 2.12.0 Downloads/month (npm): 16 172 Downloads/week (npm): 3 393 Forks (GitHub): 25 Stars (GitHub): 167 Not marked · First seen |
Not listed |
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/pubmed-mcp-server | PatentRef |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 167 | No figure on GitHub |
| Forks (GitHub) (differs) | 25 | No figure on GitHub |
| Last release (differs) | 2026-11-03 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (patentref-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 10, secrets among them: 0 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/cyanheads/pubmed-mcp-server | Not stated |
| Changes in the last 7 days (differs) | 3 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-05 |
| Endpoint at the last check (differs) | Responded 13 h 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/pubmed-mcp-server
Search PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms.
PatentRef
PatentsView-compatible US patent API: claim trees, patent briefs and search, grants 1976 to now.
How to run each
io.github.cyanheads/pubmed-mcp-server As a remote MCP server
claude mcp add --transport http pubmed-mcp-server https://pubmed.caseyjhand.com/mcp
PatentRef As a local MCP server: PyPI package
claude mcp add --env "PATENTREF_API_KEY=<YOUR_PATENTREF_API_KEY>" --transport stdio patentref-mcp -- uvx patentref-mcp
Requires: PATENTREF_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.cyanheads/pubmed-mcp-server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of PatentRef nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only io.github.cyanheads/pubmed-mcp-server asks for
MCP_AUTH_MODEMCP_HTTP_ENDPOINT_PATHMCP_HTTP_HOSTMCP_HTTP_PORTMCP_LOG_LEVELMCP_PUBLIC_URLMCP_TRANSPORT_TYPENCBI_ADMIN_EMAILNCBI_API_KEYUNPAYWALL_EMAIL
Only PatentRef asks for
PATENTREF_API_KEY (secret)PATENTREF_BASE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.cyanheads/pubmed-mcp-server · What it can do: PatentRef · 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.