io.github.faulkj/fhirhydrant
NPM · FHIRHYDRANT
FHIR MCP server with SMART Backend Services, response compaction, FHIRPath, and guarded writes.
Available components
Last scanned (23 hours ago)
Scores higher than 21% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security76
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/node 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 827 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to faulkj/fhirHydrant). View diagnostics → Pass
- License check failed: the license (Kopimi) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 68 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- CVE-2023-54404 no longer affects this package ▲ security
- 31 Oct 26 0
- CVE-2026-118773 affects this package: high ▼ security
- CVE-2026-118764 affects this package: high ▼ security
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 −1
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- Known CVEs: partial → fail ▼ security
- CVE-2026-33894 no longer affects this package ▲ security
- CVE-2026-93687 no longer affects this package ▲ security
- 15 Oct 26 0
- CVE-2026-93687 affects this package ▼ security
- 14 Oct 26 0
- CVE-2026-93687 no longer affects this package ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/fhirhydrant@0.17.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | faulkj/fhirHydrant |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/faulkj/fhirHydrant/.github/workflows/publish.yml@refs/tags/v0.17.3 |
| Rekor log index | 2620275702 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:747a25497ee00e7995d01c5d402fda25b3168c09ad0a98e2bf84eb5989d5f8aa45ca6e95d410652beb1b95ae00543128e6bff28b593b26419ff66fc08 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
| GHSA-3g3m-2fjr-6pw4 | CVE-2026-118773 | medium | yes | |
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 4 |
| Stale | 94 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the io.github.faulkj/fhirhydrant MCP server?
io.github.faulkj/fhirhydrant runs locally as an npm package, launched with npx -y fhirhydrant. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · fhirhydrant
claude mcp add faulkj-fhirhydrant -- npx -y fhirhydrant
What is the io.github.faulkj/fhirhydrant MCP server?
io.github.faulkj/fhirhydrant is an MCP server listed in the public MCP registry as io.github.faulkj/fhirhydrant. FHIR MCP server with SMART Backend Services, response compaction, FHIRPath, and guarded writes. This page covers its npm package (fhirhydrant).
Is the io.github.faulkj/fhirhydrant MCP server safe to use?
io.github.faulkj/fhirhydrant scores 40 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the io.github.faulkj/fhirhydrant MCP server still maintained?
io.github.faulkj/fhirhydrant is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.faulkj/fhirhydrant MCP server under?
io.github.faulkj/fhirhydrant declares the Kopimi licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.