io.github.faulkj/fhirhydrant
NPM · FHIRHYDRANT · SCANNED SEP 20
FHIR MCP server with SMART Backend Services, response compaction, FHIRPath, and guarded writes.
Available components
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 Security93
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects csv-parse 4.16.3, reached via fhirpath > @lhncbc/ucum-lhc > csv-parse. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 73 of 183 dependencies flagged as unhealthy (4 deprecated). 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 23 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) that our sandbox does not supply, 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) that our sandbox does not supply, 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) that our sandbox does not supply, 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) that our sandbox does not supply, 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) that our sandbox does not supply, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package 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 →
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
{
"mcpServers": {
"faulkj-fhirhydrant": {
"command": "npx",
"args": [
"-y",
"fhirhydrant"
]
}
}
} {
"servers": {
"faulkj-fhirhydrant": {
"command": "npx",
"args": [
"-y",
"fhirhydrant"
]
}
}
} codex mcp add faulkj-fhirhydrant -- npx -y fhirhydrant
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"faulkj-fhirhydrant": {
"type": "local",
"command": [
"npx",
"-y",
"fhirhydrant"
],
"enabled": true
}
}
} openclaw mcp add faulkj-fhirhydrant --command npx --arg -y --arg fhirhydrant
mcp_servers:
faulkj-fhirhydrant:
command: "npx"
args: ["-y", "fhirhydrant"] {
"McpServers": {
"faulkj-fhirhydrant": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"fhirhydrant"
]
}
}
} assistant mcp add faulkj-fhirhydrant -t stdio -c npx -a -y fhirhydrant
{
"mcpServers": {
"faulkj-fhirhydrant": {
"command": "npx",
"args": [
"-y",
"fhirhydrant"
]
}
}
} 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.
- 9 Sept 26 −1
- CVE-2026-85063 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 28 Aug 26 0
- Package version: 0.17.2 → 0.17.3 functional
- 26 Aug 26 46
First indexed and scored.
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 20 Sept 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 | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:747a25497ee00e7995d01c5d402fda25b3168c09ad0a98e2bf84eb5989d5f8aa45ca6e95d410652beb1b95ae00543128e6bff28b593b26419ff66fc08 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-8cw4-87c7-c6xx | CVE-2026-85063 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 183 packages
| Packages resolved | 183 |
|---|---|
| Deprecated | 4 |
| Stale | 73 |
| Tree resolution | Complete |
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.
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 45 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 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 20 September 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.