Skip to content

DrChrono MCP by usefulapi

io.usefulapi/drchronousefulapi.iostreamable-httpv1.41.0Scanned

Read and write DrChrono patients, appointments, offices and clinical notes.

15 tools: 2 can delete or cancel things and 13 only read.

Tools: 2 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the DrChrono MCP by usefulapi can do

The DrChrono MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (2 tools: drchrono_create_appointment and drchrono_create_patient). 13 tools only read.

1 tool reads private data (drchrono_list_clinical_notes).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.41.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 2Claude Code: deny
  • drchrono_create_appointmentDESTRUCTIVE: creates a new appointment on the schedule.No findings

    Why it is in this group

    • The name "drchrono_create_appointment" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    DESTRUCTIVE: creates a new appointment on the schedule. Requires doctor, patient, office, scheduled_time (ISO datetime), and duration (minutes). DrChrono API: POST /appointments.

    Annotations the server declares

    • title: Create appointment
    • destructiveHint: true
  • drchrono_create_patientDESTRUCTIVE: creates a new patient record.No findings

    Why it is in this group

    • The name "drchrono_create_patient" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    DESTRUCTIVE: creates a new patient record. Requires first_name, last_name, gender, date_of_birth (yyyy-mm-dd), and doctor. DrChrono API: POST /patients.

    Annotations the server declares

    • title: Create patient
    • destructiveHint: true
Only reads 13Show 13 read-only tools
  • drchrono_get_patientFetch a single patient's full demographic record by id.No findings

    Why it is in this group

    • The name "drchrono_get_patient" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single patient's full demographic record by id. DrChrono API: GET /patients/{id}.

    Annotations the server declares

    • title: Get a patient
    • readOnlyHint: true
  • drchrono_list_allergiesList patient allergies, filterable by patient or doctor.No findings

    Why it is in this group

    • The name "drchrono_list_allergies" says "list": a word for reading.
    Description, as the server wrote it
    List patient allergies, filterable by patient or doctor. Returns a page plus `next`/`previous`. DrChrono API: GET /allergies.

    Annotations the server declares

    • title: List allergies
    • readOnlyHint: true
  • drchrono_list_appointmentsList appointments.No findings

    Why it is in this group

    • The name "drchrono_list_appointments" says "list": a word for reading.
    Description, as the server wrote it
    List appointments. The DrChrono API requires at least one of `date`, `since`, or `date_range`. Further filter by doctor, patient, or office. Returns a page plus `next`/`previous`. DrChrono API: GET /appointments.

    Annotations the server declares

    • title: List appointments
    • readOnlyHint: true
  • drchrono_list_clinical_notesList clinical notes, filterable by patient, date, date range, or last-modified time.Reads private dataNo findings

    Why it is in this group

    • The name "drchrono_list_clinical_notes" says "list": a word for reading.

    What it can reach

    • private-dataThe name "drchrono_list_clinical_notes" says "list" and "note": it reads notes.
    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    List clinical notes, filterable by patient, date, date range, or last-modified time. Returns a page plus `next`/`previous`. DrChrono API: GET /clinical_notes.

    Annotations the server declares

    • title: List clinical notes
    • readOnlyHint: true
  • drchrono_list_doctorsList the providers/doctors in the practice (id, name, specialty).No findings

    Why it is in this group

    • The name "drchrono_list_doctors" says "list": a word for reading.
    Description, as the server wrote it
    List the providers/doctors in the practice (id, name, specialty). Returns a page plus `next`/`previous`. DrChrono API: GET /doctors.

    Annotations the server declares

    • title: List doctors
    • readOnlyHint: true
  • drchrono_list_lab_ordersList lab orders, filterable by doctor, patient, or last-modified time.No findings

    Why it is in this group

    • The name "drchrono_list_lab_orders" says "list": a word for reading.
    Description, as the server wrote it
    List lab orders, filterable by doctor, patient, or last-modified time. Returns a page plus `next`/`previous`. DrChrono API: GET /lab_orders.

    Annotations the server declares

    • title: List lab orders
    • readOnlyHint: true
  • drchrono_list_lab_resultsList lab results, filterable by doctor, patient, or lab order.No findings

    Why it is in this group

    • The name "drchrono_list_lab_results" says "list": a word for reading.
    Description, as the server wrote it
    List lab results, filterable by doctor, patient, or lab order. Returns a page plus `next`/`previous`. DrChrono API: GET /lab_results.

    Annotations the server declares

    • title: List lab results
    • readOnlyHint: true
  • drchrono_list_line_itemsList billing line items (charges/procedures), filterable by appointment, doctor, patient, or service date.No findings

    Why it is in this group

    • The name "drchrono_list_line_items" says "list": a word for reading.
    Description, as the server wrote it
    List billing line items (charges/procedures), filterable by appointment, doctor, patient, or service date. Returns a page plus `next`/`previous`. DrChrono API: GET /line_items.

    Annotations the server declares

    • title: List line items
    • readOnlyHint: true
  • drchrono_list_medicationsList patient medications, filterable by patient or doctor.No findings

    Why it is in this group

    • The name "drchrono_list_medications" says "list": a word for reading.
    Description, as the server wrote it
    List patient medications, filterable by patient or doctor. Returns a page plus `next`/`previous`. DrChrono API: GET /medications.

    Annotations the server declares

    • title: List medications
    • readOnlyHint: true
  • drchrono_list_officesList the practice's offices/locations.No findings

    Why it is in this group

    • The name "drchrono_list_offices" says "list": a word for reading.
    Description, as the server wrote it
    List the practice's offices/locations. Returns a page plus `next`/`previous`. DrChrono API: GET /offices.

    Annotations the server declares

    • title: List offices
    • readOnlyHint: true
  • drchrono_list_patient_paymentsList patient payments (billing), filterable by doctor, patient, or last-modified time.No findings

    Why it is in this group

    • The name "drchrono_list_patient_payments" says "list": a word for reading.
    Description, as the server wrote it
    List patient payments (billing), filterable by doctor, patient, or last-modified time. Returns a page plus `next`/`previous`. DrChrono API: GET /patient_payments.

    Annotations the server declares

    • title: List patient payments
    • readOnlyHint: true
  • drchrono_list_patientsList/search patients in the practice, filterable by doctor, name, gender, date of birth, or last-modified time.No findings

    Why it is in this group

    • The name "drchrono_list_patients" says "list": a word for reading.
    Description, as the server wrote it
    List/search patients in the practice, filterable by doctor, name, gender, date of birth, or last-modified time. Returns a page of patients plus `next`/`previous` URLs. DrChrono API: GET /patients.

    Annotations the server declares

    • title: List patients
    • readOnlyHint: true
  • drchrono_list_problemsList problem-list entries (diagnoses), filterable by patient or doctor.No findings

    Why it is in this group

    • The name "drchrono_list_problems" says "list": a word for reading.
    Description, as the server wrote it
    List problem-list entries (diagnoses), filterable by patient or doctor. Returns a page plus `next`/`previous`. DrChrono API: GET /problems.

    Annotations the server declares

    • title: List problems
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://drchrono.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://drchrono.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://drchrono.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://drchrono.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.41.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http drchrono https://drchrono.usefulapi.io/mcp
claude mcp add --transport http drchrono https://drchrono.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__drchrono__drchrono_list_patients",
      "mcp__drchrono__drchrono_get_patient",
      "mcp__drchrono__drchrono_list_appointments",
      "mcp__drchrono__drchrono_list_offices",
      "mcp__drchrono__drchrono_list_doctors",
      "mcp__drchrono__drchrono_list_clinical_notes",
      "mcp__drchrono__drchrono_list_problems",
      "mcp__drchrono__drchrono_list_medications",
      "mcp__drchrono__drchrono_list_allergies",
      "mcp__drchrono__drchrono_list_lab_results",
      "mcp__drchrono__drchrono_list_lab_orders",
      "mcp__drchrono__drchrono_list_patient_payments",
      "mcp__drchrono__drchrono_list_line_items"
    ],
    "ask": [],
    "deny": [
      "mcp__drchrono__drchrono_create_appointment",
      "mcp__drchrono__drchrono_create_patient"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as drchrono. Review it before you use it.

Capability tags behind 1 rule
  • mcp__drchrono__drchrono_list_clinical_notes private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/drchrono/verify?hash=5d0389e0b49870caecc45596ef9b93ab394614001e59185d2913653cb5c6a4d5" | jq -e '.changed == false'

Pinned hash 5d0389e0b498, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/drchrono/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/drchrono
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/drchrono.svg)](https://radar.anlyon.com/servers/io.usefulapi/drchrono)

Source: MCP Registry · repository. Synced Nov 21, 2026, 08:17 UTC.

DrChrono MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DrChrono MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DrChrono MCP by usefulapi delete data?

Yes. 2 tools can delete, cancel or revoke something: drchrono_create_appointment and drchrono_create_patient.

Can the DrChrono MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DrChrono MCP by usefulapi have?

15 tools: 2 destructive, 13 read. drchrono_create_appointment, drchrono_create_patient, drchrono_list_patients, drchrono_get_patient, drchrono_list_appointments, drchrono_list_offices, drchrono_list_doctors, drchrono_list_clinical_notes and 7 more.

Does the DrChrono MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the DrChrono MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DrChrono MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.