Healthpoint Rs

MCP其他

提供方 edithatogo

其他 未标注 API Key 社区 / 第三方 Claude DesktopClaudeCursorCodex
查看接入方式

Rust SDK, CLI, and read-only MCP server for licensed Healthpoint HL7 FHIR API access

一句话选型结论

按资料字段整理

Healthpoint Rs 属于其他类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

fhir mcp healthcare rust

支持客户端

适用场景

fhirmcphealthcare

安装与配置

未标注 API Key
上游未给出传输方式
cargo run -p healthpoint-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Healthpoint Rs当前 未标注 未标注 未标注 有 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方edithatogo上游标注的维护方 edithatogo
分类其他本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · rust本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

9.2 KB
来自项目仓库与上游目录的原文,未做删改

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```text

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:```bash
cargo install healthpoint-mcp healthpoint-cli

Install from source checkout:```bash
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```bash
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 HEALTHPOINT_MODE=live and provide HEALTHPOINT_API_KEY for licensed live API calls.

Configuration```bash

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```bash
healthpoint doctor
healthpoint policy show

healthpoint fixture services --format human
healthpoint schema service-record
healthpoint schema resource-uri

healthpoint inspect search-url \
  --text &quot;cervical screening&quot; \
  --snomed 171149006 \
  --limit 10

healthpoint search services \
  --text &quot;cervical screening&quot; \
  --snomed 171149006 \
  --limit 10 \
  --format json

healthpoint search services \
  --lat -36.8485 \
  --lon 174.7633 \
  --radius-km 10 \
  --format csv

healthpoint get service &lt;service-id&gt; --format json
healthpoint get location &lt;location-id&gt; --format json
healthpoint get organization &lt;organization-id&gt; --format json
healthpoint get uri healthpoint://service/&lt;service-id&gt; --format json

healthpoint export manifest --output .healthpoint/manifest.json
healthpoint export services \
  --text &quot;cervical screening&quot; \
  --limit 25 \
  --format jsonl \
  --output .healthpoint/cervical-screening.jsonl

Tools

Tool Purpose
healthpoint.diagnostic.status Show redacted runtime mode, configuration, and readiness.
healthpoint.access.notes Show non-secret endpoint, auth, and documentation notes.
healthpoint.access.policy Show the conservative access/export policy before reuse.
healthpoint.services.search Search HealthcareService records by text, codes, region filters, cursor, and limit.
healthpoint.services.search_snomed Search HealthcareService records by SNOMED CT code in type, category, or specialty.
healthpoint.services.nearby Find HealthcareService records near a latitude/longitude point.
healthpoint.service.get Read one HealthcareService by FHIR id.
healthpoint.location.get Read one Location by FHIR id.
healthpoint.organization.get Read one Organization by FHIR id.
healthpoint.resource.read Read a supported healthpoint:// resource URI.

The MCP server also exposes 3 static resources, 4 resource templates, and 2 prompts. See docs/mcp-tools.md and docs/integrations/mcp-client-configs.md for launch examples.

Claude Desktop source-checkout example:```json
{
"mcpServers": {
"healthpoint-dev": {
"command": "cargo",
"args": ["run", "-p", "healthpoint-mcp"],
"env": {
"HEALTHPOINT_MODE": "synthetic"
}
}
}
}


Live Healthpoint mode requires a licensed API key:```json
{
  &quot;mcpServers&quot;: {
    &quot;healthpoint-live&quot;: {
      &quot;command&quot;: &quot;healthpoint-mcp&quot;,
      &quot;env&quot;: {
        &quot;HEALTHPOINT_MODE&quot;: &quot;live&quot;,
        &quot;HEALTHPOINT_API_KEY&quot;: &quot;...&quot;,
        &quot;HEALTHPOINT_BASE_URL&quot;: &quot;https://uat.healthpointapi.com/baseR4/&quot;,
        &quot;HEALTHPOINT_AUTH_SCHEME&quot;: &quot;x-api-key&quot;
      }
    }
  }
}

Integration contracts

The CLI can emit JSON Schema for the core contracts:```bash
healthpoint schema access-policy
healthpoint schema service-query
healthpoint schema service-record
healthpoint schema service-page
healthpoint schema location-record
healthpoint schema organization-record
healthpoint schema resource-uri
healthpoint schema export-manifest


Those schemas are intended to help future integration with `open_social_data`, MCP clients, and any cross-repo data catalogue layer without prematurely forcing Healthpoint&#x27;s FHIR graph into a dataframe-first shape.

## Offline readiness tools

These commands work before any live Healthpoint validation and are useful in sandboxes or CI metadata jobs:```bash
CONDUCTOR_ALLOW_NO_CARGO=1 bin/conductor-setup
bin/conductor-status
scripts/static-preflight.py
scripts/generate-contract-schemas.py
bin/mock-healthpoint-server --port 8787

After Rust is available, the mock server gives the CLI a synthetic HTTP target:bash export HEALTHPOINT_BASE_URL=&quot;http://127.0.0.1:8787/&quot; export HEALTHPOINT_AUTH_SCHEME=&quot;none&quot; cargo run -p healthpoint-cli -- search services --snomed 171149006 --format json

See docs/mock-server.md, docs/static-preflight.md, and docs/live-contract-capture.md.

Development environment

See docs/development-environment.md for native Rust and devcontainer setup.

Design principles

  1. FHIR-first: preserve raw FHIR while exposing typed domain records.
  2. Read-only by default: no writes, no scraping fallback, no public proxy mode.
  3. Bring-your-own-key: releasing code does not bundle access or data rights.
  4. Provenance everywhere: exports carry retrieval time, source, licence status, and tool version.
  5. Integratable later: stable Rust traits make it possible to plug into open_social_data, MCP clients, and future data/catalog engines.
  6. Conductor-managed context: implementation tracks, decisions, and repo state live alongside the code.
  7. Synthetic fixtures only: offline testing is done with testkit resources, never real Healthpoint payloads.

MCP Registry metadata

  • MCP Registry name: mcp-name: io.github.edithatogo/healthpoint-rs

This visible marker is required for Cargo/crates.io ownership verification by the official MCP Registry.

Safety boundary

This is not a clinical decision-support system. It retrieves and formats directory/service information from Healthpoint for licensed users. Any downstream use should preserve Healthpoint attribution, currency, caveats, and licensing obligations.

Current status

Implementation spike after initial scaffold. Synthetic mapping exists for HealthcareService, Location, and Organization, including richer service fields such as eligibility, availability, service provision codes, characteristics, comments, endpoints, identifiers, and response provenance. The public Healthpoint material confirms HL7 FHIR and SNOMED CT orientation, but full endpoint/auth details are intentionally treated as configurable until validated against licensed API documentation.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Healthpoint Rs 怎么安装?

在客户端按下面的安装命令接入:cargo run -p healthpoint-mcp。装完在客户端配置里引用同一个包或端点。

Healthpoint Rs 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Healthpoint Rs 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Healthpoint Rs 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Healthpoint Rs 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Healthpoint Rs 能提供哪些能力?

资料显示能力标签包括 fhir、mcp、healthcare、rust。具体工具清单以官方文档为准。

Healthpoint Rs 需要什么运行环境?

运行时为 rust。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。