Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

Semble MCP by usefulapi

MCP server · semble.usefulapi.io · found in a public list · checked since 2026-10-30

Redirect not followed · latest check

As JSON

Reads and updates clinic patients, bookings, invoices and tasks in Semble.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means

Placed in Service business management: Clients, jobs, scheduling, estimates and invoices for trades, studios, coaches and other service firms.

https://semble.usefulapi.io/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person. See 582 endpoints from usefulapi.io.

Our checks

An unpaid request daily, from eastern North America

Last 2 checks, oldest to newest; room for 28 more

1 passed, 1 failed, 28 not run.

Passed, 30 daysshort history1 of 2 run
Checks missed0in 30 days
Response, latest3 msto first headers
Scheduledailyset by usage; rule below
Checked since2026-10-301 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hours00——————
7 dayssince 2026-10-3010——————
30 dayssince 2026-10-3010——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

semble_add_patient_labelsemble_create_patientsemble_create_tasksemble_get_bookingsemble_get_invoicesemble_get_patientsemble_get_practicesemble_get_productsemble_get_usersemble_list_bookingssemble_list_contactssemble_list_invoicessemble_list_labelssemble_list_patient_bookingssemble_list_patientssemble_list_productssemble_list_taskssemble_list_userssemble_update_task

Tools
19
This list since
2026-10-30
First listed to us
2026-10-30
List changes, 90 days
0

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
not observed
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
promptstools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

Calls it declares

  • semble_get_practice
  • semble_list_patients search page page_size
  • semble_get_patient id*
  • semble_list_patient_bookings patient_id* start* end* include_deleted only_cancelled page page_size
  • semble_list_bookings start end include_deleted page page_size
  • semble_get_booking id*
  • semble_list_users search clinicians_only include_deleted page page_size
  • semble_get_user id*
  • semble_list_products search page page_size
  • semble_get_product id*
  • semble_list_invoices start end status paid_or_outstanding page page_size
  • semble_get_invoice id*

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Business and productivity / Customer records / Service business management (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-30. Wrong place? Tell us.

In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✓ says what it does; ✗ its latest check did not pass.

Recent probes

WhenResultTime to headers

cloudflare:MIA		 Redirect not followed HTTP 302
initialize answered HTTP 302		 3 ms

cloudflare:EWR		 Live, handshake completed HTTP 200 14 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_360f1353b58611c1