Home / MCP registry index / io.usefulapi/splose

splose MCP by usefulapi

io.usefulapi/splose in the official MCP registry. Endpoint https://splose.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read splose patients, appointments, invoices, cases; book and cancel appointments, record payments.

We read its 36 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

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

VS Code

code --add-mcp '{"name":"splose","type":"http","url":"https://splose.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

splose_get_account splose_list_patients splose_get_patient splose_list_appointments splose_get_appointment splose_list_practitioners splose_get_practitioner splose_list_locations splose_get_location splose_list_services splose_get_service splose_list_contacts splose_get_contact splose_list_cases splose_get_case splose_list_invoices splose_get_invoice splose_list_payments splose_get_payment splose_list_payment_methods splose_list_credit_notes splose_list_waitlist splose_list_patient_forms splose_list_support_activities splose_list_busy_times splose_list_cancellation_reasons splose_list_custom_fields splose_get_practitioner_availability splose_find_free_slots splose_create_appointment splose_update_appointment splose_cancel_appointment splose_mark_patient_arrived splose_create_patient splose_create_contact splose_record_payment

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): a114e2d46efaaece. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-splose/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-splose)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.