Openevidence MCP
First open-source OpenEvidence MCP server: browser-session medical research tools for Codex, Claude Code, and MCP clients
Is Openevidence MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Openevidence MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Openevidence MCP scores 50.2/100 (Grade C), ranked #932 of 1325 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 2.5/10; 20% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Openevidence MCP compares in MCP Servers
- #531 MCP Server 12306 50.3 +0.1
- #532 Ref Tools MCP 50.2 ±0
- #533 Openevidence MCP 50.2 this agent
- #534 MCP Eu Ai Act 50.1 −0.1
- #535 Markdownify MCP 50.1 −0.1
Bars show each HVTrust score; the tick marks Openevidence MCP’s 50.2.
Where the 50.2 comes from
HVTrust dimensions vs the MCP Servers average
50.2 / 100 · 100.0% confidenceOpenevidence MCP MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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
Activity & Reach
Analysis
Activity Inputs
43.2 / 100Supply Chain Trust
Common questions about Openevidence MCP
Does Openevidence MCP publish package provenance?
Does Openevidence MCP have an OpenSSF Scorecard?
Is Openevidence MCP actively maintained?
What license does Openevidence MCP use?
Are Openevidence MCP's commits signed?
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
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 →
- browser
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Openevidence MCP'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.
Maintain Openevidence MCP?
For maintainers
HVTrust scores Openevidence MCP 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/openevidence-mcp)
<a href="https://hvtracker.net/agents/openevidence-mcp"><img src="https://hvtracker.net/badge/openevidence-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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.3 · Raw JSON