FHIR MCP Server

FHIR MCP Server – helping you expose any FHIR Server or API as a MCP Server.

MCP Servers Python Listed Apache-2.0

Is FHIR MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.8 / 10
Provenance Attested
Signed commits 63%
Last push 4d ago
Advisories None known
Compare FHIR MCP Server
Suggest a correction

In detail: FHIR MCP Server scores 78.9/100 (Grade B), ranked #198 of 1374 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.8/10; 63% of recent commits are signed; no published advisory affects its latest release (fhir-mcp-server); last pushed 2026-11-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How FHIR 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.

Chain of custody

Scanners check what the code says. This traces who ships FHIR 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.

  1. Source Partly signed

    github.com/wso2/fhir-mcp-server, Apache-2.0, last pushed 2026-11-06. 63% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.8/10 (scanned Oct 29, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection6
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Linked and attested

    • PyPI fhir-mcp-server Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: fhir-mcp-server 0.11.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-30 OSSF Scorecard: 4.7/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 FHIR 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.

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 FHIR MCP Server compares in MCP Servers

  1. #108 MCP Adr Analysis Server 79.2 +0.3
  2. #109 Coolify MCP 79.1 +0.2
  3. #110 FHIR MCP Server 78.9 this agent
  4. #111 Monarch MCP Server 78.8 −0.1
  5. #112 EduBase MCP 78.8 −0.1

Bars show each HVTrust score; the tick marks FHIR MCP Server’s 78.9.

Where the 78.9 comes from

HVTrust dimensions vs the MCP Servers average

78.9 / 100 · 100.0% confidence

FHIR MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.7 / 25
5.9 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
17.5 / 20
5.3 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.1 / 20
1.5 above avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-11-06
Rank Moved
Rank rose 11 spots (#212 → #201)
2026-10-29
Rank Moved
Rank rose 65 spots (#267 → #202)
2026-10-29
HVTrust Changed
HVTrust up 3.9pts (74.4 → 78.3)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent
View MCP Servers Report missing data
63.8
Activity sub-score · out of 100
#110

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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 4 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
137
Forks
59
Last Push
2026-11-06
4 days ago
Commits (4 wk)
27
Downloads (7d)
913
pypi
HN mentions (30d)
—
Open Issues
4
Rank Change
=
was #198

Analysis

Activity Inputs

63.8 / 100
StarsRepository reach
12.8 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
18.1 / 25
CommunityFork signal
8.3 / 20

Common questions about FHIR MCP Server

Public supply-chain signals for FHIR MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but FHIR MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does FHIR MCP Server publish package provenance?
Yes. FHIR MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does FHIR MCP Server have an OpenSSF Scorecard?
FHIR MCP Server has an OpenSSF Scorecard score of 4.8/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 FHIR MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does FHIR MCP Server use?
FHIR MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are FHIR MCP Server's commits signed?
63% of the last 100 commits to FHIR 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
high confidence
Implemented
FHIR MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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 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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

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
Rank 27HVTrust 4Score 4Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-06
Rank Moved
Rank rose 11 spots (#212 → #201)
2026-10-29
Rank Moved
Rank rose 65 spots (#267 → #202)
2026-10-29
HVTrust Changed
HVTrust up 3.9pts (74.4 → 78.3)
2026-10-29
Activity Score Changed
Activity score up 9pts (54 → 62)
2026-10-21
Rank Moved
Rank rose 27 spots (#277 → #250)
2026-10-14
Rank Moved
Rank rose 10 spots (#289 → #279)
2026-10-13
Rank Moved
Rank dropped 38 spots (#251 → #289)
2026-10-12
Rank Moved
Rank rose 62 spots (#313 → #251)
2026-10-12
Activity Score Changed
Activity score up 7pts (48 → 56)
2026-10-04
Rank Moved
Rank dropped 11 spots (#298 → #309)
2026-10-01
Rank Moved
Rank dropped 31 spots (#264 → #295)
2026-09-30
Rank Moved
Rank rose 49 spots (#313 → #264)
2026-09-30
Activity Score Changed
Activity score up 5pts (48 → 53)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 696 spots (#996 → #300)
2026-09-23
HVTrust Changed
HVTrust up 46.5pts (25.0 → 71.5)
2026-09-22
Newly Listed
First tracked at rank #996
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-10
Rank Moved
Rank rose 11 spots (#285 → #274)
2026-09-08
Rank Moved
Rank dropped 13 spots (#264 → #277)
2026-09-07
Rank Moved
Rank dropped 14 spots (#250 → #264)
2026-09-06
Rank Moved
Rank dropped 27 spots (#223 → #250)
2026-09-05
Rank Moved
Rank dropped 54 spots (#169 → #223)
2026-09-04
Rank Moved
Rank rose 57 spots (#226 → #169)
2026-09-04
HVTrust Changed
HVTrust up 4.4pts (69.2 → 73.6)
2026-09-04
Activity Score Changed
Activity score up 13pts (39 → 52)
2026-09-03
Rank Moved
Rank dropped 12 spots (#214 → #226)
2026-08-31
Rank Moved
Rank dropped 25 spots (#183 → #208)
2026-08-30
Scorecard Added
OSSF Scorecard: 4.7/10
2026-08-30
Grade Changed
Trust grade C → B
2026-08-30
Rank Moved
Rank rose 216 spots (#399 → #183)
2026-08-30
HVTrust Changed
HVTrust up 9.9pts (59.6 → 69.5)
2026-08-29
Rank Moved
Rank dropped 16 spots (#383 → #399)
2026-08-27
Rank Moved
Rank dropped 10 spots (#373 → #383)
2026-08-26
Rank Moved
Rank dropped 36 spots (#337 → #373)
2026-08-24
Rank Moved
Rank dropped 17 spots (#317 → #334)
2026-08-22
Rank Moved
Rank rose 17 spots (#333 → #316)
2026-08-19
Rank Moved
Rank dropped 18 spots (#314 → #332)
2026-08-17
Rank Moved
Rank rose 15 spots (#330 → #315)
2026-08-13
Rank Moved
Rank dropped 37 spots (#282 → #319)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 78.9 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/fhir-mcp-server.svg)](https://hvtracker.net/agents/fhir-mcp-server)
HTML:
<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

Data sources
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.4 · Raw JSON