Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FHIR MCP Server

PYPI · FHIR-MCP-SERVER

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Available components

0 this week 44 Trust /100

Last scanned (11 hours ago)

Scores higher than 41% of PyPI servers

Category Health and Science

Trust breakdown (7 categories)

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 Security82
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects aiohttp 3.13.5, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 3 of 48 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to wso2/fhir-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • 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), 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 →

What we tested

Checks we ran (9)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (5)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)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.
  • Stability in Stability & Change Management (scores 0 for this)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.
  • Tool coverage in Tool Coverage (scores 0 for this)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.
  • Tool safety in Tool Safety (scores 0 for this)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.
  • Capabilities in Capabilities (scores 0 for this)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.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +15
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-128128 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-128131 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-128125 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-128132 affects this package: high ▼ security
    • CVE-2026-128126 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-128127 affects this package: high ▼ security
    • CVE-2026-123817 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-128124 affects this package: high ▼ security
    • CVE-2026-115563 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-128130 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-128129 affects this package: high ▼ security
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 0
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-128128 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-128131 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-128125 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-128132 affects this package: high ▼ security
    • CVE-2026-128126 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-128127 affects this package: high ▼ security
    • CVE-2026-123817 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-128124 affects this package: high ▼ security
    • CVE-2026-115563 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-128130 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-128129 affects this package: high ▼ security
  • 19 Nov 26 0
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-128128 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-128131 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-128125 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-128132 affects this package: high ▼ security
    • CVE-2026-128126 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-128127 affects this package: high ▼ security
    • CVE-2026-123817 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-128124 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-128130 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-128129 affects this package: high ▼ security
  • 18 Nov 26 −15
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-128128 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-128131 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-128125 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-128132 affects this package: high ▼ security
    • CVE-2026-128126 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-128127 affects this package: high ▼ security
    • CVE-2026-123817 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-128124 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-128130 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-128129 affects this package: high ▼ security
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +15
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-128128 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-128131 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-128125 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-128132 affects this package: high ▼ security
    • CVE-2026-128126 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-128127 affects this package: high ▼ security
    • CVE-2026-123817 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-128124 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-128130 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-128129 affects this package: high ▼ security
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
  • 14 Nov 26 +15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 13 Nov 26 −15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

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 21 Nov 2026 · Analysed pypi/fhir-mcp-server@0.11.0

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo wso2/fhir-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/wso2/fhir-mcp-server/.github/workflows/release.yaml@refs/tags/0.11.0
Rekor log index 3560518668
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:219747d334efdf18e7d2a5c4ffc7f683360dbf06fdb2f473987ce7d012a1d7c9

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 69 findings
ID CVE Severity Vector Fix available
GHSA-24c4-3p7v-29cm CVE-2026-128127 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-28qf-cpwq-vmc2 CVE-2026-128130 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H yes
GHSA-2fqr-mr3j-6wp8 CVE-2026-54279 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-2g87-pp6c-29x5 CVE-2026-123817 high yes
GHSA-3rp8-rxj8-mvjw CVE-2026-128128 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-494j-54xm-rwp3 CVE-2026-111063 medium yes
GHSA-4fvr-rgm6-gqmc CVE-2026-54273 medium yes
GHSA-4m7w-qmgq-4wj5 CVE-2026-54275 low yes
GHSA-5pv8-vvhc-h7jv CVE-2026-128125 medium yes
GHSA-5rmc-48h2-hvcm CVE-2026-128132 high yes
GHSA-5wr8-gcqf-gqf3 CVE-2026-111064 high yes
GHSA-63hw-fmq6-xxg2 CVE-2026-54277 medium yes
GHSA-6cjc-53gc-5rqm CVE-2026-111065 medium yes
GHSA-9x8q-7h8h-wcw9 CVE-2026-54280 low yes
GHSA-9xw5-w5jj-pvcg CVE-2026-111066 high yes
GHSA-cq5v-8q36-5273 CVE-2026-69244 high yes
GHSA-f9xw-jh8m-3mwq CVE-2026-111748 medium yes
GHSA-g3cq-j2xw-wf74 CVE-2026-54278 medium yes
GHSA-gx76-c99x-2c96 CVE-2026-111749 low yes
GHSA-h4cc-hm5h-fmm9 CVE-2026-128131 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-hg6j-4rv6-33pg CVE-2026-47265 medium yes
GHSA-hpj7-wq8m-9hgp CVE-2026-54276 medium yes
GHSA-jg22-mg44-37j8 CVE-2026-34993 medium CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:L yes
GHSA-jm3w-gw2p-xjfj CVE-2026-128124 high yes
GHSA-m6qw-4cw2-hm4m CVE-2026-50269 low yes
GHSA-mfx4-hv73-q22v CVE-2026-69243 medium yes
GHSA-mq44-7p77-q5h7 CVE-2026-59881 medium yes
GHSA-pqxq-w44r-73xw CVE-2026-111750 medium yes
GHSA-pw86-h8fm-j323 CVE-2026-128129 high yes
GHSA-xcgm-r5h9-7989 CVE-2026-54274 medium yes
GHSA-xgw8-8ccx-rmqh CVE-2026-128126 high yes
PYSEC-2026-2104 CVE-2026-34993 high CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2105 CVE-2026-47265 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-2106 CVE-2026-50269 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2107 CVE-2026-54273 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2108 CVE-2026-54274 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2109 CVE-2026-54276 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
PYSEC-2026-2110 CVE-2026-54277 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2111 CVE-2026-54278 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2112 CVE-2026-54279 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2113 CVE-2026-54280 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-237 CVE-2026-54275 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3545 CVE-2026-69244 none yes
PYSEC-2026-3546 CVE-2026-69243 none yes
PYSEC-2026-3547 CVE-2026-59881 none yes
PYSEC-2026-4365 CVE-2026-111063 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
PYSEC-2026-4366 CVE-2026-111064 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-4367 CVE-2026-111065 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
PYSEC-2026-4368 CVE-2026-111066 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-4369 CVE-2026-111748 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N yes

Showing 50 of 69 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

Dependencies 48 packages
Packages resolved 48
Stale 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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.

Install

How do I install the FHIR MCP Server server?

FHIR MCP Server runs locally as a PyPI package, launched with uvx fhir-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · fhir-mcp-server

# add to Claude Code
claude mcp add wso2-fhir-mcp-server -- uvx fhir-mcp-server
Common questions

What is the FHIR MCP Server server?

FHIR MCP Server is listed in the public MCP registry as io.github.wso2/fhir-mcp-server. MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications. This page covers its PyPI package (fhir-mcp-server).

Is the FHIR MCP Server server safe to use?

FHIR MCP Server scores 44 out of 100 on VerifyMCP. We recorded 69 known advisories against it as of 21 November 2026. 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 FHIR MCP Server server still maintained?

FHIR MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 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 FHIR MCP Server server under?

FHIR MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the FHIR MCP Server server?

VerifyMCP ran 9 checks on FHIR MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about FHIR MCP Server: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.