Home / MCP registry index / io.usefulapi/akute-health
Akute Health MCP by usefulapi
io.usefulapi/akute-health in the official MCP registry.
Endpoint https://akute-health.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Akute Health patients, appointments, tasks, notes, medications, allergies and observations.
We read its 15 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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
akutehealth_search_patients akutehealth_get_patient akutehealth_list_appointments akutehealth_get_appointment akutehealth_list_appointment_types akutehealth_get_availability akutehealth_list_tasks akutehealth_get_task akutehealth_list_notes akutehealth_get_note akutehealth_list_medications akutehealth_list_allergies akutehealth_list_observations akutehealth_list_practitioners akutehealth_get_practitioner
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-akute-health)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.