Name: FHIR
Author: wso2

FHIR MCP

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

Grade A Local · stdio No auth needed 7 tools v0.10.0

No reviews yet by wso2PyPI 17,572 Runs on your machine, nothing hosted

100/100

trust score

downloads a day

local

runs on your machine

506

downloads in 30d

What it does

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

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'FHIR_SERVER_BASE_URL=${FHIR_SERVER_BASE_URL}' --transport stdio wso2-fhir-mcp '--' uvx fhir-mcp-server

# 2 — ask your agent for something these tools do
#   get_capabilities, search, read and 4 more

It needs FHIR_SERVER_BASE_URL: this reads it from your environment, so export it first.

FHIR costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publisher

wso21 server

1 category

All 1 server

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts FHIR as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads FHIR_SERVER_BASE_URL (Base URL of the FHIR Server (eg: https://hapi.fhir.org/baseR5)) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx FHIR_SERVER_BASE_URL … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'FHIR_SERVER_BASE_URL=${FHIR_SERVER_BASE_URL}' --transport stdio wso2-fhir-mcp '--' uvx fhir-mcp-server

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs settings only you can give it: FHIR_SERVER_BASE_URL — Base URL of the FHIR Server (eg: https://hapi.fhir.org/baseR5). You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Retrieves metadata about a specified FHIR resource type, including its supported search parameters and custom operations. This tool MUST always be invoked before performing any resource operation (such as search, read, create, update, or delete) to discover the valid searchParams and operations…

Parameter	Type	Required	Notes
type	string	yes	The FHIR resource type name. Must exactly match one of the core or profile-defined resource types as per the FHIR specification.

Executes a standard FHIR search interaction on a given resource type, returning a bundle or list of matching resources. Use this when you need to query for multiple resources based on one or more search-parameters. Do not use this tool for create, update, or delete operations, and be aware that…

Parameter	Type	Required	Notes
type	string	yes	The FHIR resource type name. Must exactly match one of the resource types supported by the server
searchParam	object	yes	A mapping of FHIR search parameter names to their values. Only include parameters supported for the resource type, as listed by get_capabilities.
response_filter_fhirpaths	array	no	Specify FHIRPath expressions to filter the response to only the data you need. Omitting returns the full resource.

Performs a FHIR read interaction to retrieve a single resource instance by its type and resource ID, optionally refining the response with search parameters or custom operations. Use it when you know the exact resource ID and require that one resource; do not use it for bulk queries. If…

Parameter	Type	Required	Notes
type	string	yes	The FHIR resource type name. Must exactly match one of the resource types supported by the server.
id	string	yes	The logical ID of a specific FHIR resource instance.
searchParam	object	no	A mapping of FHIR search parameter names to their desired values. These parameters refine queries for operation-specific query qualifiers. Only parameters exposed by get_capabilities for that resour
operation	string	no	The name of a custom FHIR operation or extended query defined for the resource must match one of the operation names returned by get_capabilities.
response_filter_fhirpaths	array	no	Specify FHIRPath expressions to filter the response to only the data you need. Omitting returns the full resource. Bundle.* expressions supported with $everything.

Creates a new FHIR resource on the server (FHIR create interaction: POST [base]/{type}). Use it to add a record that does not exist yet, such as a new Patient, Observation or Appointment. Do not use it to change an existing resource; use update for that. The server assigns a new id on every…

Parameter	Type	Required	Notes
type	string	yes	The FHIR resource type name. Must exactly match one of the resource types supported by the server.
payload	object	yes	The JSON body of the new resource. Include every element the resource's profile marks as required, or the server rejects the request. Set resourceType to the same value as type; if omitted, it def
searchParam	object	no	A mapping of FHIR search parameter names to their desired values. These parameters refine queries for operation-specific query qualifiers. Only parameters exposed by get_capabilities for that resour
operation	string	no	The name of a custom FHIR operation or extended query defined for the resourceMust match one of the operation names returned by get_capabilities.

Replaces the full content of an existing FHIR resource (FHIR update interaction: PUT [base]/{type}/{id}). Use it to correct or complete a record whose logical id you already know. Elements left out of the payload are removed from the stored resource, not kept, so first get the current version…

Parameter	Type	Required	Notes
type	string	yes	The FHIR resource type name. Must exactly match one of the resource types supported by the server.
id	string	yes	The logical ID of a specific FHIR resource instance.
payload	object	yes	The complete new content of the resource. It replaces the stored version entirely, so include every required element and all existing data you want to keep. Set resourceType to the same value as `ty
searchParam	object	no	A mapping of FHIR search parameter names to their desired values. These parameters refine queries for operation-specific query qualifiers. Only parameters exposed by get_capabilities for that resour
operation	string	no	The name of a custom FHIR operation or extended query defined for the resourceMust match one of the operation names returned by get_capabilities.

Execute a FHIR delete interaction on a specific resource instance. Use this tool when you need to remove a single resource identified by its logical ID or optionally filtered by search parameters. The optional id parameter must match an existing resource instance when present. If you include…

Parameter	Type	Required	Notes
type	string	yes	The FHIR resource type name. Must exactly match one of the resource types supported by the server.
id	string	no	The logical ID of a specific FHIR resource instance.
searchParam	object	no	A mapping of FHIR search parameter names to their desired values. These parameters refine queries for operation-specific query qualifiers. Only parameters exposed by get_capabilities for that resour
operation	string	no	The name of a custom FHIR operation or extended query defined for the resourceMust match one of the operation names returned by get_capabilities.

Retrieves the authenticated user's FHIR profile. Use this tool when you need to access the current user's demographic and contact details.

No parameter schema on file.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under Apache-2.0
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install FHIR or to call it, at any volume.

ATrust score 100 / 100

Release 0.10.0 · scanned 15 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score100

Findings2 threat · 0 capability

Capabilityminimal

Coveragesource

Verificationsource

Surface digest6e73e223e67548773be69ab5081c87d0ca9af38a41f2db3f8c6c2db0834c4810

Score vectorthreat 100 → client 100

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
verification-discount	source	publisher verification (provenance) — cryptographic build provenance ties the artifact to its source	−0
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
get_capabilities	untrusted-input	untrusted-input: keyword "fetch"
search	no tags
read	no tags
create	no tags
update	no tags
delete	no tags
get_user	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest6e73e223e6754877

Scanned2026-10-15

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.