MCP.Market

healthpoint-rs MCP server

by edithatogo·io.github.edithatogo/healthpoint-rs·v0.1.0·1 stars

Read-only MCP server for licensed Healthpoint HL7 FHIR API access.

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed healthpoint-rs yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

healthpoint-rs tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How healthpoint-rs compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 39% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Install healthpoint-rs in Claude Code, Cursor or VS Code

claude mcp add healthpoint-rs -- docker run -i --rm ghcr.io/edithatogo/healthpoint-mcp:0.1.0
Add to Cursor

What the publisher says

From the healthpoint-rs repository's README, as published. We do not edit it. Read it on GitHub

healthpoint-rs

Rust-first tooling for the Healthpoint HL7 FHIR® API: a typed client, CLI, read-only MCP server, and future open-social-data adapter.

This repository is intentionally code-first and data-light:

  • Users bring their own Healthpoint API key/licence.
  • No real Healthpoint API payloads are committed as fixtures.
  • Synthetic FHIR fixtures live in crates/healthpoint-testkit/fixtures/.
  • Local exports are marked with provenance and redistribution status.
  • Open-data publication is opt-in and disabled until licensing/access terms explicitly permit it.

Project shape

healthpoint-rs/
  crates/
    healthpoint-core/         # domain model, query model, provenance, provider traits, URI parsing
    healthpoint-fhir/         # FHIR Bundle/Resource mapping and typed projections
    healthpoint-client/       # HTTP client, auth, request policy, pagination hooks
    healthpoint-export/       # JSON/JSONL/CSV/export manifests
    healthpoint-cli/          # `healthpoint` CLI
    healthpoint-mcp/          # read-only MCP server over the same core/client
    healthpoint-osd-adapter/  # future open_social_data bridge, no hard dependency yet
    healthpoint-testkit/      # synthetic fixtures and offline fixture provider
  conductor/                  # context-management state, decisions, checkpoints, tracks
  docs/                       # access, licensing, MCP, exports, integration roadmap

Installation

Install from crates.io after Rust is available:

cargo install healthpoint-mcp healthpoint-cli

Install from source checkout:

git clone https://github.com/edithatogo/healthpoint-rs.git
cd healthpoint-rs
bin/conductor-setup
cargo install --path crates/healthpoint-mcp
cargo install --path crates/healthpoint-cli

Install through Smithery from the published listing: edithatogo/healthpoint-rs. The Smithery package starts in synthetic mode unless live Healthpoint credentials are supplied.

Usage

First commands

cp .env.example .env
$EDITOR .env
bin/conductor-setup
cargo run -p healthpoint-cli -- doctor
cargo run -p healthpoint-cli -- fixture services --format json
cargo run -p healthpoint-cli -- inspect search-url --text "cervical screening" --snomed 171149006
cargo run -p healthpoint-cli -- search services --text "cervical screening" --format json
cargo run -p healthpoint-cli -- search services --snomed 171149006 --format json
cargo run -p healthpoint-cli -- get service <id> --format json
cargo run -p healthpoint-cli -- get uri healthpoint://service/<id> --format json
cargo run -p healthpoint-mcp

The MCP server is a separate binary so CLI and MCP can evolve independently while sharing the same crates. It starts in synthetic fixture mode when no API key is supplied; set HEALTHPOINTMODE=live and provide HEALTHPOINTAPI_KEY for licensed live API calls.

Configuration

export HEALTHPOINT_MODE="synthetic"                       # synthetic | live
export HEALTHPOINT_API_KEY="..."                         # optional; required only for live mode
export HEALTHPOINT_BASE_URL="https://uat.healthpointapi.com/baseR4/"
export HEALTHPOINT_AUTH_SCHEME="x-api-key"               # bearer | x-api-key | header:<name> | none
export HEALTHPOINT_GEO_SEARCH_MODE="healthpoint-lat-lon" # healthpoint-lat-lon | fhir-near
export HEALTHPOINT_TIMEOUT_SECS="30"
export HEALTHPOINT_EXPORT_POLICY="local-only"            # local-only | licensed-share | open-approved

Healthpoint portal validation on 2026-06-30 confirmed UAT calls use the x-api-key header against https://uat.healthpointapi.com/baseR4/. See docs/healthpoint-api-access.md for observed endpoint and license notes.

CLI examples

healthpoint doctor
healthpoint policy show

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

healthpoint-rs: common questions

Is healthpoint-rs MCP server safe?
Mostly: it is graded B (73/100). Read the healthpoint-rs safety report
How do I install healthpoint-rs?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does healthpoint-rs need an API key?
Yes. The registry entry asks for HEALTHPOINT_API_KEY.
Is healthpoint-rs maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.1.0.
How does healthpoint-rs compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.

More from edithatogo →