FHIR MCP Server
FHIR MCP Server – helping you expose any FHIR Server or API as a MCP Server.
Is FHIR MCP Server safe? Promising trust profile, but some evidence still deserves review.
Compare FHIR MCP Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: FHIR MCP Server scores 71.3/100 (Grade B), ranked #308 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.2/10; 67% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →
How FHIR MCP Server compares in MCP Servers
- #182 Gnosis MCP 71.4 +0.1
- #183 Fred MCP Server 71.3 ±0
- #184 FHIR MCP Server 71.3 this agent
- #185 MCP Open Library 71.3 ±0
- #186 Proxmox VE MCP Server 71.3 ±0
Bars show each HVTrust score; the tick marks FHIR MCP Server’s 71.3.
Where the 71.3 comes from
HVTrust dimensions vs the MCP Servers average
71.3 / 100 · 100.0% confidenceFHIR MCP Server 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 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
Activity & Reach
Analysis
Activity Inputs
48.8 / 100Supply Chain Trust
Common questions about FHIR MCP Server
Does FHIR MCP Server publish package provenance?
Does FHIR MCP Server have an OpenSSF Scorecard?
Is FHIR MCP Server actively maintained?
What license does FHIR MCP Server use?
Are FHIR MCP Server'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 →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to FHIR 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.
Maintain FHIR MCP Server?
For maintainers
HVTrust scores FHIR 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/fhir-mcp-server)
<a href="https://hvtracker.net/agents/fhir-mcp-server"><img src="https://hvtracker.net/badge/fhir-mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON