List your agent

splose MCP by usefulapi

MCP server · hosted · v1.0.0 · io.usefulapi/splose
Online · tested 1h agoNEW · 2h agoSeen in the registry 1h ago

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

Website ↗Source code ↗How to connect ↓

What it does

splose MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to 3 capabilities: invoicing, meeting scheduling and payments. That makes it a candidate for tasks such as book sales meetings or detect fraudulent transactions.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen24 Oct 2026
Last checked1h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoint

  • https://splose.usefulapi.io/mcp streamable-http

In Claude Code: claude mcp add --transport http splose-mcp-by-usefulapi https://splose.usefulapi.io/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE splose MCP by usefulapi answered an MCP connection on 24 Oct 2026 and introduced itself as splose-mcp 1.0.0 (MCP protocol 2025-06-18).

36 tools offered to AI assistants

  • 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 the full record. HEALTH DATA: only look people up when the user asks. GET /patie
  • 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_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, practitione
  • 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 /contacts.
Show 24 more
  • 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. HEALTH/FUNDING DATA. GET /cases.
  • 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 items and payment ids. Use status=Awaiting Payment for what is owed. GET /invoices.
  • 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. GET /patient-forms.
  • 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 roster, not the open slots: use splose_find_free_slots for bookable times. GET /av
  • 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_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 appoin
  • 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 th
  • 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 sett
  • 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/{patient
  • 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 cre
  • 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 contact
  • 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 spl

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Tasks it helps with

Share of each task's required capabilities it covers
Book sales meetings
Meeting Scheduling
50%
Detect fraudulent transactions
Payments
50%
Send and chase invoices
Invoicing
50%
Schedule meetings
Meeting Scheduling
50%
Screen job applicants
Meeting Scheduling
50%
Reconcile payments
Payments
33%
Buy products online
Payments
33%
Handle refund requests
Payments
33%

Similar tools

Listed for the same task: book sales meetings
  • GhostPaw EmailREMOTELOCAL
    Email tools with a local SQLite cache and IMAP/SMTP account configuration
  • Trumpia MCP by usefulapiREMOTELOCAL
    Read Trumpia lists, subscribers, keywords and reports; add contacts and send SMS or email campaigns
  • YouCanBook.me MCP by usefulapiREMOTELOCAL
    Manage YouCanBook.me bookings, booking pages, appointment types, team members and locations
  • NexHealth MCP by usefulapiREMOTELOCAL
    Read and write NexHealth appointments, patients, providers and locations
  • SendGrid MCP by usefulapiREMOTELOCAL
    Send email and read templates, marketing contacts, lists, stats, bounces and unsubscribes
  • Nookal MCP by usefulapiREMOTELOCAL
    Read Nookal locations, practitioners, availability, appointments, clients, cases and invoices

Ready-made AI agents

An MCP server is a connector you add to your own assistant. These are finished products that do the same job for you:

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://splose.usefulapi.io/mcpDECLAREDSRC-001 Official MCP Registry1h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1h ago
Websitehttps://usefulapi.io/splose/DECLAREDSRC-001 Official MCP Registry1h ago
Repositoryhttps://github.com/m190/usefulapi-mcpDECLAREDSRC-001 Official MCP Registry1h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1h ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry1h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1h ago

Change history

  • NEW24 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Questions about splose MCP by usefulapi

How do I connect splose MCP by usefulapi?

Use the hosted endpoint https://splose.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does splose MCP by usefulapi offer?

When Electra Index connected on 24 Oct 2026, it listed 36 tools: splose_get_account, splose_list_patients, splose_get_patient, splose_list_appointments, splose_get_appointment, splose_list_practitioners, splose_get_practitioner, splose_list_locations and more. The full list is in "Live check" above.

Is splose MCP by usefulapi online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.

What can I use splose MCP by usefulapi for?

Based on its description, it is most relevant to: book sales meetings, detect fraudulent transactions, send and chase invoices, schedule meetings.