Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/edithatogo/healthpoint-rsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/edithatogo/healthpoint-rs/mcp-healthpoint)<a href="https://agentmods.dev/mcp/edithatogo/healthpoint-rs/mcp-healthpoint"><img src="https://agentmods.dev/badge/mcp/edithatogo/healthpoint-rs/mcp-healthpoint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/edithatogo/healthpoint-rs/mcp-healthpoint"><img src="https://agentmods.dev/badge/mcp/edithatogo/healthpoint-rs/mcp-healthpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
healthpoint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"healthpoint": {
"command": "healthpoint-mcp",
"env": {
"HEALTHPOINT_API_KEY": "${HEALTHPOINT_API_KEY}",
"HEALTHPOINT_BASE_URL": "https://www.healthpointapi.com/",
"HEALTHPOINT_AUTH_SCHEME": "bearer",
"HEALTHPOINT_GEO_SEARCH_MODE": "healthpoint-lat-lon"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 11 lines scan A 66260006eb67
healthpoint is an MCP server published in the GitHub repository edithatogo/healthpoint-rs (1 stars, last pushed 8d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp
Securely access and manage FHIR healthcare data stored in Medplum. Remote server at api.medplum.com.
tirith-gateway
MCP server "tirith-gateway" as configured in sheeki03/tirith. Launched with tirith gateway run --upstream-bin tirith --upstream-arg mcp-server --config ~/.c.
scraps
MCP server "scraps", hosted remotely, as configured in boykush/scraps.
healthclaw-local
MCP server "healthclaw-local", hosted remotely at localhost, as configured in aks129/HealthClawGuardrails.
healthclaw-guardrails
Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation. Remote server at mcp-server-production-5112.up.railway.app.
remem
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. Runs locally from the @remem-ai/remem npm package.