Remote MCP · Endpoint

Acuity Scheduling MCP by usefulapi MCP server

No. Acuity Scheduling MCP by usefulapi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://acuity-scheduling.usefulapi.io/mcp

The last check completed an MCP handshake.

Registry name
io.usefulapi/acuity-scheduling
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
215 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Read appointments, types, calendars and availability; create, cancel or reschedule bookings.
Listing
From the official MCP registry (active).
Recent checks of Acuity Scheduling MCP by usefulapi
CheckedResultHandshake
1 hour agoHandshake completed215 ms
2 days agoHandshake completed196 ms
4 days agoHandshake completed174 ms
6 days agoHandshake completed195 ms
7 days agoHandshake completed176 ms
9 days agoHandshake completed227 ms
10 days agoHandshake completed602 ms
11 days agoHandshake completed298 ms
14 days agoHandshake completed268 ms
15 days agoHandshake completed141 ms
17 days agoHandshake completed375 ms
19 days agoHandshake completed241 ms
20 days agoHandshake completed179 ms
21 days agoHandshake completed143 ms
22 days agoHandshake completed250 ms
22 days agoHandshake completed48 ms
23 days agoHandshake completed221 ms
25 days agoHandshake completed243 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Acuity Scheduling MCP by usefulapi and makes no claim about it beyond what these checks measured.