Is Pubmed MCP Server safe to use?

Pubmed MCP Server has an HVTrust score of 69.0/100 (Grade B), ranked #372 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Pubmed MCP Server?

Pubmed MCP Server scores 69.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 159 GitHub stars and is categorized under MCP Servers.

Pubmed MCP Server

Repository by cyanheads

Search PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms via MCP. STDIO or Streamable HTTP.

MCP Servers TypeScript Listed Apache-2.0

Is Pubmed MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.0 / 10

Provenance None

Signed commits 100%

Last push 2d ago

Advisories None known

Compare Pubmed MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Pubmed MCP Server scores 69.0/100 (Grade B), ranked #372 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.0/10; 100% of recent commits are signed; no published advisory affects its latest release (@cyanheads/pubmed-mcp-server); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pubmed MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Publish build provenance for its packagesnpm publish --provenance from CI +14.5 → 83.5 A · #39 of 781
Raise the OSSF Scorecard from 6.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +6.2 → 75.2 B · #137 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Pubmed MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/cyanheads/pubmed-mcp-server, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.0/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 10

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 9
Published packages Linked, not attested
- npm @cyanheads/pubmed-mcp-server Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: @cyanheads/pubmed-mcp-server 2.10.20. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

2026-09-17 OSSF Scorecard: 5.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Pubmed MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Pubmed MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Pubmed MCP Server’s 69.0.

Where the 69.0 comes from

HVTrust dimensions vs the MCP Servers average

69.0 / 100 · 100.0% confidence

Pubmed MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

12.5 / 25

2.1 above avg 10.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.7 below avg 13.5

Transparency50% declared license · 50% OSSF Scorecard

13.6 / 17

1.4 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.4 / 20

7.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

10.0 / 20

2.6 above avg 7.4

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-04

Rank Moved

Rank rose 25 spots (#370 → #345)

2026-10-03

Rank Moved

Rank dropped 12 spots (#358 → #370)

2026-09-28

Mcp Status Changed

Detected MCP server support changed: implemented → declared

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Pubmed MCP Server View MCP Servers Report missing data

68.0

Activity sub-score · out of 100

#220

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars

159

Forks

Last Push

2026-10-09

2 days ago

Commits (4 wk)

Downloads (7d)

3,590

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼5

was #367

Analysis

Activity Inputs

68.0 / 100

StarsRepository reach

13.2 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

23.4 / 25

CommunityFork signal

6.5 / 20

Common questions about Pubmed MCP Server

Pubmed MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Pubmed MCP Server publish package provenance?

No published build provenance is currently detected for Pubmed MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Pubmed MCP Server have an OpenSSF Scorecard?

Pubmed MCP Server has an OpenSSF Scorecard score of 6.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Pubmed MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does Pubmed MCP Server use?

Pubmed MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Pubmed MCP Server's commits signed?

100% of the last 100 commits to Pubmed MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Pubmed MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-28

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Pubmed MCP Server?

For maintainers

HVTrust scores Pubmed MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-10-04

Rank Moved

Rank rose 25 spots (#370 → #345)

2026-10-03

Rank Moved

Rank dropped 12 spots (#358 → #370)

2026-09-28

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-09-28

Rank Moved

Rank dropped 35 spots (#315 → #350)

2026-09-25

Rank Moved

Rank rose 36 spots (#348 → #312)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 399 spots (#744 → #345)

2026-09-23

HVTrust Changed

HVTrust up 39.0pts (30.1 → 69.1)

2026-09-22

Newly Listed

First tracked at rank #744

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 10 spots (#356 → #366)

2026-09-17

Scorecard Added

OSSF Scorecard: 5.1/10

2026-09-17

Grade Changed

Trust grade D → B

2026-09-17

Rank Moved

Rank rose 805 spots (#1167 → #362)

2026-09-17

HVTrust Changed

HVTrust up 28.7pts (39.7 → 68.4)

2026-09-09

Activity Score Changed

Activity score up 5pts (57 → 62)

2026-09-08

Rank Moved

Rank dropped 14 spots (#1158 → #1172)

2026-09-07

Rank Moved

Rank dropped 16 spots (#1142 → #1158)

2026-09-06

Rank Moved

Rank dropped 13 spots (#1129 → #1142)

2026-09-05

Rank Moved

Rank dropped 36 spots (#1093 → #1129)

2026-09-04

Rank Moved

Rank dropped 23 spots (#1070 → #1093)

2026-09-03

Rank Moved

Rank dropped 29 spots (#1041 → #1070)

2026-09-02

Rank Moved

Rank rose 174 spots (#1215 → #1041)

2026-09-02

HVTrust Changed

HVTrust up 14.7pts (22.5 → 37.2)

2026-09-01

Rank Moved

Rank dropped 30 spots (#1185 → #1215)

2026-08-31

Rank Moved

Rank dropped 27 spots (#1158 → #1185)

2026-08-30

Rank Moved

Rank dropped 38 spots (#1120 → #1158)

2026-08-29

Rank Moved

Rank dropped 41 spots (#1079 → #1120)

2026-08-28

Rank Moved

Rank dropped 34 spots (#1045 → #1079)

2026-08-27

Rank Moved

Rank dropped 21 spots (#1024 → #1045)

2026-08-26

Rank Moved

Rank dropped 85 spots (#939 → #1024)

2026-08-25

Rank Moved

Rank dropped 34 spots (#905 → #939)

2026-08-25

Activity Score Changed

Activity score down 6pts (62 → 56)

2026-08-24

Rank Moved

Rank dropped 10 spots (#895 → #905)

2026-08-21

Rank Moved

Rank rose 43 spots (#939 → #896)

2026-08-17

Rank Moved

Rank rose 13 spots (#950 → #937)

2026-08-16

Rank Moved

Rank dropped 30 spots (#920 → #950)

2026-08-13

Rank Moved

Rank dropped 14 spots (#909 → #923)

2026-08-12

Rank Moved

Rank rose 12 spots (#921 → #909)

2026-08-10

Rank Moved

Rank dropped 53 spots (#863 → #916)

2026-08-08

Newly Listed

First tracked at rank #849

GitHub → npm: @cyanheads/pubmed-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/pubmed-mcp-server.svg)](https://hvtracker.net/agents/pubmed-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/pubmed-mcp-server"><img src="https://hvtracker.net/badge/pubmed-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Pubmed MCP Server

How Pubmed MCP Server could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Pubmed MCP Server compares in MCP Servers

Where the 69.0 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Pubmed MCP Server

AI agent surface

Maintain Pubmed MCP Server?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers