Skip to content

Cliniko MCP by usefulapi

io.usefulapi/clinikousefulapi.iostreamable-httpv1.41.4Scanned

Hosted MCP server for Cliniko — patients, appointments, availability, and invoices for AI agents.

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

Tools: 2 delete, 0 irreversible, 0 write, 15 read.
  • Reads private data · 2
  • 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 Cliniko MCP by usefulapi can do

The Cliniko MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (2 tools: cliniko_create_patient and cliniko_create_appointment). 15 tools only read.

2 tools read private data (cliniko_list_treatment_notes and cliniko_get_treatment_note).

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.4.

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.

17 tools

Deletes or cancels 2Claude Code: deny
  • cliniko_create_appointmentWRITE — books a REAL new individual appointment in the live Cliniko practice.No findings

    Why it is in this group

    • The name "cliniko_create_appointment" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE — books a REAL new individual appointment in the live Cliniko practice. Requires patient_id, practitioner_id, business_id, appointment_type_id, and starts_at (ISO 8601). ends_at defaults from the appointment type if omitted. POST /individual_appointments.

    Annotations the server declares

    • title: Create an appointment
    • destructiveHint: true
  • cliniko_create_patientWRITE — creates a REAL new patient record in the live Cliniko practice.No findings

    Why it is in this group

    • The name "cliniko_create_patient" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE — creates a REAL new patient record in the live Cliniko practice. Requires first_name + last_name. POST /patients.

    Annotations the server declares

    • title: Create a patient
    • destructiveHint: true
Only reads 15Show 15 read-only tools
  • cliniko_get_accountGet the Cliniko account and subscription details for the authenticated API key.No findings

    Why it is in this group

    • The name "cliniko_get_account" says "get": a word for reading.
    Description, as the server wrote it
    Get the Cliniko account and subscription details for the authenticated API key. A good first call to sanity-check auth, shard, and User-Agent. GET /account.

    Annotations the server declares

    • title: Get account details
    • readOnlyHint: true
  • cliniko_get_appointmentFetch a single individual appointment by id.No findings

    Why it is in this group

    • The name "cliniko_get_appointment" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single individual appointment by id. GET /individual_appointments/{id}.

    Annotations the server declares

    • title: Get an appointment
    • readOnlyHint: true
  • cliniko_get_invoiceFetch a single invoice by id.No findings

    Why it is in this group

    • The name "cliniko_get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single invoice by id. GET /invoices/{id}.

    Annotations the server declares

    • title: Get an invoice
    • readOnlyHint: true
  • cliniko_get_patientFetch a single patient by id.No findings

    Why it is in this group

    • The name "cliniko_get_patient" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single patient by id. GET /patients/{id}.

    Annotations the server declares

    • title: Get a patient
    • readOnlyHint: true
  • cliniko_get_treatment_noteFetch a single treatment note by id.Reads private dataNo findings

    Why it is in this group

    • The name "cliniko_get_treatment_note" says "get": a word for reading.

    What it can reach

    • private-dataThe name "cliniko_get_treatment_note" says "get" and "note": it reads notes.
    • private-dataThe description's first sentence says "fetch" and "note": it reads notes.
    Description, as the server wrote it
    Fetch a single treatment note by id. NOTE: treatment notes are protected health information (PHI). Read-only. GET /treatment_notes/{id}.

    Annotations the server declares

    • title: Get a treatment note
    • readOnlyHint: true
  • cliniko_list_appointment_typesList appointment types (service definitions).No findings

    Why it is in this group

    • The name "cliniko_list_appointment_types" says "list": a word for reading.
    Description, as the server wrote it
    List appointment types (service definitions). GET /appointment_types.

    Annotations the server declares

    • title: List appointment types
    • readOnlyHint: true
  • cliniko_list_appointmentsList individual appointments, optionally filtered by patient/practitioner/business/type and a starts_at date-time window (starts_from / starts_to, ISO 8601).No findings

    Why it is in this group

    • The name "cliniko_list_appointments" says "list": a word for reading.
    Description, as the server wrote it
    List individual appointments, optionally filtered by patient/practitioner/business/type and a starts_at date-time window (starts_from / starts_to, ISO 8601). GET /individual_appointments.

    Annotations the server declares

    • title: List appointments
    • readOnlyHint: true
  • cliniko_list_available_timesList bookable appointment slots for a business + practitioner + appointment type within a date range (from/to, yyyy-mm-dd, span <= 7 days).No findings

    Why it is in this group

    • The name "cliniko_list_available_times" says "list": a word for reading.
    Description, as the server wrote it
    List bookable appointment slots for a business + practitioner + appointment type within a date range (from/to, yyyy-mm-dd, span <= 7 days). High-value booking-slot lookup. GET /businesses/{business_id}/practitioners/{practitioner_id}/appointment_types/{appointment_type_id}/available_times.

    Annotations the server declares

    • title: List available times
    • readOnlyHint: true
  • cliniko_list_businessesList businesses (practice locations) in the account.No findings

    Why it is in this group

    • The name "cliniko_list_businesses" says "list": a word for reading.
    Description, as the server wrote it
    List businesses (practice locations) in the account. GET /businesses.

    Annotations the server declares

    • title: List businesses
    • readOnlyHint: true
  • cliniko_list_invoicesList invoices, optionally filtered by patient.No findings

    Why it is in this group

    • The name "cliniko_list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices, optionally filtered by patient. GET /invoices.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • cliniko_list_patientsSearch/list patients.No findings

    Why it is in this group

    • The name "cliniko_list_patients" says "list": a word for reading.
    Description, as the server wrote it
    Search/list patients. Name/email filters use Cliniko 'contains' matching (q[]=field:~value). GET /patients.

    Annotations the server declares

    • title: List patients
    • readOnlyHint: true
  • cliniko_list_practitionersList practitioners in the account.No findings

    Why it is in this group

    • The name "cliniko_list_practitioners" says "list": a word for reading.
    Description, as the server wrote it
    List practitioners in the account. GET /practitioners.

    Annotations the server declares

    • title: List practitioners
    • readOnlyHint: true
  • cliniko_list_productsList billable products/items.No findings

    Why it is in this group

    • The name "cliniko_list_products" says "list": a word for reading.
    Description, as the server wrote it
    List billable products/items. GET /products.

    Annotations the server declares

    • title: List products
    • readOnlyHint: true
  • cliniko_list_treatment_notesList treatment notes, optionally filtered by patient.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "cliniko_list_treatment_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 treatment notes, optionally filtered by patient. NOTE: treatment notes are protected health information (PHI) — handle with care. Read-only. GET /treatment_notes.

    Annotations the server declares

    • title: List treatment notes
    • readOnlyHint: true
  • cliniko_next_available_timeGet the single next bookable slot for a business + practitioner + appointment type (optionally from a date).No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get the single next bookable slot for a business + practitioner + appointment type (optionally from a date). GET /businesses/{business_id}/practitioners/{practitioner_id}/appointment_types/{appointment_type_id}/next_available_time.

    Annotations the server declares

    • title: Next available time
    • 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 data2
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:34 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://cliniko.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://cliniko.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://cliniko.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://cliniko.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.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http cliniko https://cliniko.usefulapi.io/mcp
claude mcp add --transport http cliniko https://cliniko.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__cliniko__cliniko_get_account",
      "mcp__cliniko__cliniko_list_patients",
      "mcp__cliniko__cliniko_get_patient",
      "mcp__cliniko__cliniko_list_appointments",
      "mcp__cliniko__cliniko_get_appointment",
      "mcp__cliniko__cliniko_list_practitioners",
      "mcp__cliniko__cliniko_list_businesses",
      "mcp__cliniko__cliniko_list_appointment_types",
      "mcp__cliniko__cliniko_list_products",
      "mcp__cliniko__cliniko_list_invoices",
      "mcp__cliniko__cliniko_get_invoice",
      "mcp__cliniko__cliniko_list_treatment_notes",
      "mcp__cliniko__cliniko_get_treatment_note",
      "mcp__cliniko__cliniko_list_available_times",
      "mcp__cliniko__cliniko_next_available_time"
    ],
    "ask": [],
    "deny": [
      "mcp__cliniko__cliniko_create_patient",
      "mcp__cliniko__cliniko_create_appointment"
    ]
  }
}

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 cliniko. Review it before you use it.

Capability tags behind 2 rules
  • mcp__cliniko__cliniko_list_treatment_notes private-data
  • mcp__cliniko__cliniko_get_treatment_note 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/cliniko/verify?hash=50fc13fe5b09f756303aedf479ec102620356206aab35f2d8a1259f3e494e879" | jq -e '.changed == false'

Pinned hash 50fc13fe5b09, 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/cliniko/changes.xml

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

Badge

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

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Cliniko MCP by usefulapi: questions and answers

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

Is the Cliniko MCP by usefulapi safe?

No scan can promise that. What its definitions show: 17 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 Cliniko MCP by usefulapi delete data?

Yes. 2 tools can delete, cancel or revoke something: cliniko_create_patient and cliniko_create_appointment.

Can the Cliniko 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 Cliniko MCP by usefulapi have?

17 tools: 2 destructive, 15 read. cliniko_create_patient, cliniko_create_appointment, cliniko_get_account, cliniko_list_patients, cliniko_get_patient, cliniko_list_appointments, cliniko_get_appointment, cliniko_list_practitioners and 9 more.

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

Its remote endpoint did not answer the last anonymous look.

Does the Cliniko 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 Cliniko MCP by usefulapi changed its tools?

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