Home / MCP registry index / io.tooloracle/healthguard
io.tooloracle/healthguard
io.tooloracle/healthguard in the official MCP registry.
Endpoint https://tooloracle.io/health/mcp/. Source: github.com/ToolOracle/healthguard.
The registry describes it as: HealthGuard - 12-tool health/medical AI safety MCP: PII redaction, HIPAA, GDPR Art.9.
We read its 12 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
mdr_compliance_check ivdr_check device_classification udi_validate drug_interaction icd10_lookup adverse_event_report gdpr_health_check hipaa_vs_gdpr clinical_trial_phases gmp_checklist medical_calendar_eu
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-tooloracle-healthguard)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.