Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cliniko MCP by usefulapi

REMOTE · CLINIKO.USEFULAPI.IO

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

−59 this week 18 Trust /100

Last scanned (5 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 −62
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “check_the_cliniko_account_and_subscription_details” functional
    • New prompt “find_open_appointment_slots_for_a_practitioner” functional
    • New prompt “get_the_next_available_time_for_a_service” functional
    • New prompt “list_your_practice_locations_and_practitioners” functional
    • New prompt “review_the_services_and_products_you_bill” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.31.0 → 1.33.0 functional
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.2 → 1.30.0 functional
  • 30 Oct 26 0
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 0
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
  • 28 Oct 26 0
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 0
    • Server version: 1.24.0 → 1.25.0 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 0
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.0 → 1.23.0 functional
    • Server version: 1.21.3 → 1.22.0 functional
    • Server version: 1.21.0 → 1.21.3 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://cliniko.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cliniko.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cliniko.usefulapi.io/mcp Redirected 302 https://usefulapi.io/cliniko/
http (plaintext) http://cliniko.usefulapi.io/mcp Inconclusive 302 http://cliniko.usefulapi.io/mcp
MCP tools · 17 exposed · ~1,600 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cliniko_create_appointment ~173

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.

NameTypeReqDescription
appointment_type_id–yesAppointment type id (required).
business_id–yesBusiness id (required).
ends_atstring–End time, ISO 8601. Defaults from the appointment type if omitted.
notesstring–Appointment notes.
patient_id–yesPatient id (required).
practitioner_id–yesPractitioner id (required).
starts_atstringyesStart time, ISO 8601 e.g. 2026-07-20T09:00:00Z (required).

No output schema declared.

No examples provided.

cliniko_create_patient ~174

WRITE — creates a REAL new patient record in the live Cliniko practice. Requires first_name + last_name. POST /patients.

NameTypeReqDescription
address_1string–Street address line 1.
citystring–City.
country_codestring–ISO country code, e.g. AU.
date_of_birthstring–Date of birth yyyy-mm-dd.
emailstring–Email address.
first_namestringyesPatient first name (required).
last_namestringyesPatient last name (required).
notesstring–Free-text notes.
phone_numberstring–A phone number (stored as a Mobile phone number).
post_codestring–Post / ZIP code.
statestring–State / region.

No output schema declared.

No examples provided.

cliniko_get_account ~43

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cliniko_get_appointment ~35

Fetch a single individual appointment by id. GET /individual_appointments/{id}.

NameTypeReqDescription
id–yesIndividual appointment id.

No output schema declared.

No examples provided.

cliniko_get_invoice ~31

Fetch a single invoice by id. GET /invoices/{id}.

NameTypeReqDescription
id–yesInvoice id.

No output schema declared.

No examples provided.

cliniko_get_patient ~30

Fetch a single patient by id. GET /patients/{id}.

NameTypeReqDescription
id–yesPatient id.

No output schema declared.

No examples provided.

cliniko_get_treatment_note ~51

Fetch a single treatment note by id. NOTE: treatment notes are protected health information (PHI). Read-only. GET /treatment_notes/{id}.

NameTypeReqDescription
id–yesTreatment note id.

No output schema declared.

No examples provided.

cliniko_list_appointment_types ~59

List appointment types (service definitions). GET /appointment_types.

NameTypeReqDescription
pageinteger–Page number (1-based). Default 1.
per_pageinteger–Results per page (max 100). Default 50.

No output schema declared.

No examples provided.

cliniko_list_appointments ~213

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.

NameTypeReqDescription
appointment_type_id––Filter by appointment type id.
business_id––Filter by business id.
orderstring–Sort direction. asc | desc.
pageinteger–Page number (1-based). Default 1.
patient_id––Filter by patient id (q[]=patient_id:=).
per_pageinteger–Results per page (max 100). Default 50.
practitioner_id––Filter by practitioner id.
sortstring–Field to sort by, e.g. created_at.
starts_fromstring–Only appointments starting at/after this ISO 8601 time (q[]=starts_at:>).
starts_tostring–Only appointments starting before this ISO 8601 time (q[]=starts_at:<).

No output schema declared.

No examples provided.

cliniko_list_available_times ~156

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.

NameTypeReqDescription
appointment_type_id–yesAppointment type id (path).
business_id–yesBusiness id (path).
fromstringyesRange start yyyy-mm-dd (cannot be more than 7 days before `to`).
practitioner_id–yesPractitioner id (path).
tostringyesRange end yyyy-mm-dd (cannot be more than 7 days after `from`).

No output schema declared.

No examples provided.

cliniko_list_businesses ~61

List businesses (practice locations) in the account. GET /businesses.

NameTypeReqDescription
pageinteger–Page number (1-based). Default 1.
per_pageinteger–Results per page (max 100). Default 50.

No output schema declared.

No examples provided.

cliniko_list_invoices ~105

List invoices, optionally filtered by patient. GET /invoices.

NameTypeReqDescription
orderstring–Sort direction. asc | desc.
pageinteger–Page number (1-based). Default 1.
patient_id––Filter by patient id (q[]=patient_id:=).
per_pageinteger–Results per page (max 100). Default 50.
sortstring–Field to sort by, e.g. created_at.

No output schema declared.

No examples provided.

cliniko_list_patients ~145

Search/list patients. Name/email filters use Cliniko 'contains' matching (q[]=field:~value). GET /patients.

NameTypeReqDescription
emailstring–Filter by email (contains match).
first_namestring–Filter by first name (contains match).
last_namestring–Filter by last name (contains match).
orderstring–Sort direction. asc | desc.
pageinteger–Page number (1-based). Default 1.
per_pageinteger–Results per page (max 100). Default 50.
sortstring–Field to sort by, e.g. created_at.

No output schema declared.

No examples provided.

cliniko_list_practitioners ~61

List practitioners in the account. GET /practitioners.

NameTypeReqDescription
pageinteger–Page number (1-based). Default 1.
per_pageinteger–Results per page (max 100). Default 50.

No output schema declared.

No examples provided.

cliniko_list_products ~55

List billable products/items. GET /products.

NameTypeReqDescription
pageinteger–Page number (1-based). Default 1.
per_pageinteger–Results per page (max 100). Default 50.

No output schema declared.

No examples provided.

cliniko_list_treatment_notes ~98

List treatment notes, optionally filtered by patient. NOTE: treatment notes are protected health information (PHI) — handle with care. Read-only. GET /treatment_notes.

NameTypeReqDescription
pageinteger–Page number (1-based). Default 1.
patient_id––Filter by patient id (q[]=patient_id:=).
per_pageinteger–Results per page (max 100). Default 50.

No output schema declared.

No examples provided.

cliniko_next_available_time ~110

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.

NameTypeReqDescription
appointment_type_id–yesAppointment type id (path).
business_id–yesBusiness id (path).
fromstring–Optional earliest date yyyy-mm-dd to search from.
practitioner_id–yesPractitioner id (path).

No output schema declared.

No examples provided.

Install

How do I install the Cliniko MCP by usefulapi server?

Cliniko MCP by usefulapi is a hosted endpoint at https://cliniko.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · cliniko.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-cliniko 'https://cliniko.usefulapi.io/mcp'
Common questions

What is the Cliniko MCP by usefulapi server?

Cliniko MCP by usefulapi is listed in the public MCP registry as io.usefulapi/cliniko. Hosted MCP server for Cliniko, patients, appointments, availability, and invoices for AI agents. This page covers its hosted endpoint (https://cliniko.usefulapi.io/mcp).

Is the Cliniko MCP by usefulapi server safe to use?

Cliniko MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Cliniko MCP by usefulapi server expose?

Cliniko MCP by usefulapi exposes 17 tools: cliniko_get_account, cliniko_list_patients, cliniko_get_patient, cliniko_list_appointments, cliniko_get_appointment, and 12 more. Their descriptions and schemas cost roughly 1,600 tokens of context every time the server is loaded.

Does the Cliniko MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Cliniko MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Cliniko MCP by usefulapi server still maintained?

Cliniko MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.