splose MCP by usefulapi
https://splose.usefulapi.io/mcpRead splose patients, appointments, invoices, cases; book and cancel appointments, record payments.
What we measured
Over the last 30 days we probed this MCP server 21 times on 20 days; it answered 21 (100%). Median response 162 ms, 95th percentile 262 ms.
When we called tools/list it returned 36 tools, including splose_get_account, splose_list_patients, splose_get_patient, over MCP protocol revision 2025-06-18.
Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 84% and higher on readiness than 80%.
From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure
Tools (36)
As returned by the server's own tools/list when we called it.
- 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_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…
- 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 /pat…
- 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, Complete…
- splose_get_appointment
- One appointment in full, with each patient's status, case, invoice and cancellation details. GET /appointments/{id}.
- splose_list_practitioners
- Practitioners (staff): name, email, profession, role, active flag, online-booking flag, timezone and their location/service connections. GET /practitioners.
- splose_get_practitioner
- One practitioner in full, including provider numbers and connections. GET /practitioners/{id}.
- splose_list_locations
- Practice locations: title, address, phone, email, timezone, online-booking flag and the ids of the services offered there. GET /locations.
- splose_get_location
- One location in full. GET /locations/{id}.
- 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_get_service
- One service in full, including provider-travel pricing. GET /services/{id}.
- 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 /contact…
- splose_get_contact
- One contact in full. GET /contacts/{id}.
- 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…
- splose_get_case
- One case in full, with its appointment connections. GET /cases/{id}.
- splose_list_invoices
- Invoices: number, issue/due dates, patient, contact, location, practitioner, subtotal, tax, total, paid amount, status (Draft, Awaiting Payment, Paid), line ite…
- splose_get_invoice
- One invoice in full with its line items and payments. GET /invoices/{id}.
- splose_list_payments
- Payments received: payment number, amount, date, patient, location, payment method, the invoices each payment settles and credit allocations. GET /payments.
- splose_get_payment
- One payment in full. GET /payments/{id}.
- 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_credit_notes
- Credit notes: number, invoice, patient, subtotal, tax, total, sent status, items and allocations. GET /credit-notes.
- splose_list_waitlist
- Waitlist entries: patient, practitioner, location, wanted services, preferred days and time, tags and active flag. GET /waitlists.
- 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. GE…
- 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_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_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_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 ro…
- 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 practi…
- 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 bookin…
- 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 pat…
- 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 creat…
- 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…
- 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 pr…
- 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_co…
- 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.…
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B+, 94.7/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (394 ms). |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 21/21 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 36 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Compared with peers
Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 86 · peer median 81
- Latency
- Faster than 84% of peers
- This listing 134 ms · peer median 349 ms
Where it loses the most points, and how to win them back
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
- Protocol revision −4
— Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
- Verified identity −3
— Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Adoption signals
Public signals from outside this directory, shown for context. They do not change search order or grades.
Listed in
Directories this entry was found in.
How to connect
https://splose.usefulapi.io/mcp
curl -X POST https://splose.usefulapi.io/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'