npm TypeScript not analyzable deep scan unknown

pubmed-mcp-server

v2.10.5
npm

not analyzable — no source code found to analyze

Search PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms.

maintainer
cyanheads
licence
Apache-2.0
first seen
2026-05-22
last seen
2026-09-12
releases · 30d
13
short id
risk insufficient evidence

Insufficient evidence to grade. This server's source has not been statically analyzed, so a low grade would only mean "nothing found", not "nothing there". We don't show a reassuring grade we can't stand behind. Attested signals (CVEs, provenance) below still apply.

Once the source is analyzed (see the analysis flag in the header), a graded score appears here. How analysis works: methodology.

risk trajectory 11 movements
  • A · 11 A · 14
  • A · 0 A · 11
  • A · 7 A · 0
  • A · 12 A · 7
  • B · 26 A · 12
  • B · 21 B · 26
  • B · 16 B · 21
  • B · 20 B · 16
  • B · 15 B · 20
  • B · 20 B · 15
  • B · 26 B · 20
capability exposure grade factor +10
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

other grade factors evidence elsewhere
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/smithery:cyanheads/pubmed-mcp-server/badge.svg)](https://mcpobservatory.com/servers/smithery:cyanheads/pubmed-mcp-server/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of cyanheads.