splose MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

splose MCP by usefulapi is answering right now. Last checked 8 min ago. It exposes 36 tools. Last commit 25 Oct 2026.

Read splose patients, appointments, invoices, cases; book and cancel appointments, record payments.

Uptime history 21 hours of history

21 hours agonow

100.0%

Uptime 24h

76 of 76 checks

Tools

read from the server

349 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.

25 Oct a tool changed version3 times that day

and 2 more, back to 25 October 2026

Nothing serious here today

Today is the operative word: we check splose MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://splose.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.splose]
url = "https://splose.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "splose": {
      "url": "https://splose.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "splose": {
      "type": "http",
      "url": "https://splose.usefulapi.io/mcp"
    }
  }
}

Available tools 36

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

splose

splose_cancel_appointment

WRITE: cancels ONE appointment with a cancellation reason (ids from splose_list_cancellation_reasons) and an optional note. The reason's billable rate may create a cancellation charge, and the patient may be notified per the practice's settings. For a group appointment pass patient_id to cancel only that patient's place; without it the whole appointment is cancelled. Cannot be undone through this server: confirm with the user first and pass confirm: true. POST /appointments/{id}/cancellation or /appointments/{id}/patients/{patientId}/cancellation.

splose_create_appointment

WRITE: books ONE appointment for one patient with one practitioner, service and location, from start to end (UTC). Splose may send the patient its normal booking confirmation or reminders according to the practice's settings, and the appointment can later be invoiced. Check splose_find_free_slots first. Not idempotent: calling twice books twice. POST /appointments.

splose_create_contact

WRITE: adds ONE contact (GP, plan manager, referrer, payer). type, name and email are required (type is Splose's contact type, e.g. Standard; see splose_list_contacts for the values in use). Not idempotent: calling twice creates two contacts. POST /contacts.

splose_create_patient

WRITE: adds ONE new patient record (first and last name required). Search with splose_list_patients first to avoid a duplicate. Patient messaging follows the practice's settings and communicationPreference. Not idempotent: calling twice creates two patients. HEALTH DATA: only enter what the user supplied. POST /patients.

splose_find_free_slots

Bookable free slots for one or more practitioners at a location for one patient service, between from and to (the window is at most 7 days). Returns, per practitioner, the start/end of each open slot in UTC. Read-only. GET /free-slots.

splose_get_account

The organisation and the practitioner who owns the API key, plus the key's expiry date. Good first call. GET /me.

splose_get_appointment

One appointment in full, with each patient's status, case, invoice and cancellation details. GET /appointments/{id}.

splose_get_case

One case in full, with its appointment connections. GET /cases/{id}.

splose_get_contact

One contact in full. GET /contacts/{id}.

splose_get_invoice

One invoice in full with its line items and payments. GET /invoices/{id}.

splose_get_location

One location in full. GET /locations/{id}.

splose_get_patient

One patient in full: contact details, address, NDIS number and plan info, Medicare/health fund, emergency contact, tags and custom fields. HEALTH DATA. GET /patients/{id}.

splose_get_payment

One payment in full. GET /payments/{id}.

splose_get_practitioner

One practitioner in full, including provider numbers and connections. GET /practitioners/{id}.

splose_get_practitioner_availability

A practitioner's working-hours availability per date and location (start/end time, weekly or fortnightly repeat). The window is at most 100 days. This is the roster, not the open slots: use splose_find_free_slots for bookable times. GET /availabilities/{practitionerId}.

splose_get_service

One service in full, including provider-travel pricing. GET /services/{id}.

splose_list_appointments

Appointments in id order: start/end (UTC), service, location, practitioner, price, note and the per-patient status (Arrived, Did not arrive, Cancelled, Completed, cancellation reason, invoice id). Filter by time window, patient, practitioner or status. GET /appointments.

splose_list_busy_times

Blocked-out time in practitioner calendars (leave, admin time): start/end, location, practitioners, type and note. GET /busy-times.

splose_list_cancellation_reasons

Cancellation reasons with their ids, needed to cancel an appointment. GET /cancellation-reasons.

splose_list_cases

Cases (funding referrals and plans): case number, budget, hours or appointment allowance, issue and expiry dates, tracking type, open flag and utilisation alert. HEALTH/FUNDING DATA. GET /cases.

splose_list_contacts

Contacts (GPs, plan managers, referrers, invoice recipients): name, type, email, address, phones and the ids of their patients, invoices and cases. GET /contacts.

splose_list_credit_notes

Credit notes: number, invoice, patient, subtotal, tax, total, sent status, items and allocations. GET /credit-notes.

splose_list_custom_fields

The custom fields defined for patients: id, name, type (short text, dropdown, date and so on), required flag and options. GET /custom-field/.

splose_list_invoices

Invoices: number, issue/due dates, patient, contact, location, practitioner, subtotal, tax, total, paid amount, status (Draft, Awaiting Payment, Paid), line items and payment ids. Use status=Awaiting Payment for what is owed. GET /invoices.

splose_list_locations

Practice locations: title, address, phone, email, timezone, online-booking flag and the ids of the services offered there. GET /locations.

splose_list_patient_forms

Forms sent to patients: title, status (Incomplete, In progress, Completed), patient, appointment, template and submission time. The form content is included. GET /patient-forms.

splose_list_patients

Patients (clients) of the practice, filtered, in id order, as short rows: id, name, email, birthdate, phones, tags, alert, archived. Use splose_get_patient for the full record. HEALTH DATA: only look people up when the user asks. GET /patients.

splose_list_payment_methods

Payment methods (cash, card, bank transfer and so on) with their ids, needed to record a payment. GET /payment-methods.

splose_list_payments

Payments received: payment number, amount, date, patient, location, payment method, the invoices each payment settles and credit allocations. GET /payments.

splose_list_practitioners

Practitioners (staff): name, email, profession, role, active flag, online-booking flag, timezone and their location/service connections. GET /practitioners.

splose_list_services

The service catalogue: name, type, code, duration (minutes), unit (Hour or Each), price, tax type, group size and tags. GET /services.

splose_list_support_activities

Non-appointment billable activities (NDIS support activities): patient, practitioner, service, item code, quantity, price, invoice id. GET /support-activities.

splose_list_waitlist

Waitlist entries: patient, practitioner, location, wanted services, preferred days and time, tags and active flag. GET /waitlists.

splose_mark_patient_arrived

WRITE: marks the patient of ONE appointment as arrived (check-in). For a group appointment pass patient_id to mark just that patient. Marking twice has the same effect. POST /appointments/{id}/arrival or /appointments/{id}/patients/{patientId}/arrival.

splose_record_payment

WRITE, MONEY: records ONE payment received (cash, card, transfer) against ONE invoice; it moves the invoice towards Paid and is shown in the patient's account. It does NOT charge anyone's card. amount must not exceed what is owed (check splose_get_invoice). Not idempotent: calling twice records two payments, and this server cannot delete a payment, so confirm the details with the user first and pass confirm: true. Ids come from splose_get_invoice and splose_list_payment_methods. POST /payments.

splose_update_appointment

WRITE: changes the time, service, location, practitioner, case or patient of ONE existing appointment; send only the fields to change. Splose may notify the patient of a change according to the practice's settings. Same input twice gives the same result. PUT /appointments/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://splose.usefulapi.io/mcp	streamable-http	answering	426 ms	8 min ago

Alternatives to splose MCP by usefulapi

same job, measured the same way

IntakeQ MCP by usefulapi

by usefulapi

Search clients, appointments, intakes, notes and invoices in IntakeQ, and book or cancel visits.

19 tools answering

SmartAccounts MCP by usefulapi

by usefulapi

Read SmartAccounts clients, vendors, invoices, payments, ledger, accounts; create and book records.

18 tools answering

Nookal MCP by usefulapi

by usefulapi

Read Nookal locations, practitioners, availability, appointments, clients, cases and invoices.

11 tools answering

Teachworks MCP by usefulapi

by usefulapi

Read Teachworks students, families, tutors, lessons, invoices and payments; book lessons.

24 tools answering

Cliniko MCP by usefulapi

by usefulapi

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

17 tools answering

Hint Health MCP by usefulapi

by usefulapi

Read Hint Health patients, memberships, plans, invoices and payments for direct primary care.

17 tools answering

Bookingmood MCP by usefulapi

by usefulapi

Read Bookingmood bookings, availability, guests, payments and invoices; update bookings, contacts.

21 tools answering

Bill4Time MCP by usefulapi

by usefulapi

Read Bill4Time clients, projects, time entries, expenses, invoices, payments, users and contacts.

8 tools answering

splose MCP by usefulapi — questions

Answers built from our own checks of this server.

What can splose MCP by usefulapi do?

It exposes 36 tools, read directly from the server on our last check. Among them: splose_cancel_appointment, splose_create_appointment, splose_create_contact, splose_create_patient, splose_find_free_slots, splose_get_account and 30 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is splose MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 76 of 76 checks got a reply (100.0%), average response time 349 ms. The bar chart above shows every period we have measured.

How do I connect splose MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does splose MCP by usefulapi need an API key?

No. splose MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 36 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is splose MCP by usefulapi?

It answers our handshake in 349 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is splose MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at splose.usefulapi.io, which runs on its operator's own terms.