mcp server
healthpoint-rs
Read-only MCP server for licensed Healthpoint HL7 FHIR API access.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Most recent push to the repository was 2026-08-04.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 1 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-04 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 17 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-30 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | Apache-2.0 | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-06-30 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
MCHS NWAU Calculator
— last commit 2026-07-31, shares healthcare, software, solo-maintainer
Stdio MCP server for MCHS schemas, validation, support status, and evidence.
-
FYI MCP
— last commit 2026-08-06, shares cli, software, solo-maintainer
FYI request management with tools for requests, authorities, correspondence, sync, and health.
-
OSF CLI Go
— last commit 2026-08-01, shares cli, software, solo-maintainer
Read-only MCP tools for authenticated Open Science Framework projects and files.
-
com.medplum/mcp
— last commit 2026-08-06, shares fhir, healthcare
Securely access and manage FHIR healthcare data stored in Medplum.
-
io.github.aks129/healthclaw-guardrails
— last commit 2026-08-06, shares fhir, healthcare
Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation
-
Last EHR — Medplum
— last commit 2026-07-27, shares fhir, healthcare
FHIR chart tools for MCP: read-only by default, with elicitation-gated, human-approved writes.
-
Sourceright
— last commit 2026-08-07, shares cli, rust, solo-maintainer
Reference verification MCP server for CSL bibliographies, evidence, and audited writes.
-
Chiplab
— last commit 2026-08-06, shares software
Run, build, and validate firmware on virtual hardware from your AI agent. Hardware knowledge corpus.
-
com.stackscan/mcp-server
— last commit 2026-08-04, shares api-client
Look up the technology stack behind any domain, and the company running it.
-
io.ausdata/ausdata-mcp
— last commit 2026-05-20, shares api-client
28 tools over 9 AU gov data sources (ABS, RBA, ATO, APRA, AIHW, ASIC, AEMO, BOM, WGEA) via one key.
These share tags the maintainers applied themselves, such as healthcare, software, solo-maintainer, cli. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: api-client, cli, fhir, healthcare, healthpoint, mcp, rust, software, solo-maintainer.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab