Home / MCP registry index / io.usefulapi/drchrono
DrChrono MCP by usefulapi
io.usefulapi/drchrono in the official MCP registry.
Endpoint https://drchrono.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read and write DrChrono patients, appointments, offices and clinical notes.
We read its 15 tools on 2026-10-26. 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
drchrono_list_patients drchrono_get_patient drchrono_list_appointments drchrono_list_offices drchrono_list_doctors drchrono_list_clinical_notes drchrono_list_problems drchrono_list_medications drchrono_list_allergies drchrono_list_lab_results drchrono_list_lab_orders drchrono_list_patient_payments drchrono_list_line_items drchrono_create_appointment drchrono_create_patient
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-drchrono)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.