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.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 215 ms |
| 2 days ago | Handshake completed | 196 ms |
| 4 days ago | Handshake completed | 174 ms |
| 6 days ago | Handshake completed | 195 ms |
| 7 days ago | Handshake completed | 176 ms |
| 9 days ago | Handshake completed | 227 ms |
| 10 days ago | Handshake completed | 602 ms |
| 11 days ago | Handshake completed | 298 ms |
| 14 days ago | Handshake completed | 268 ms |
| 15 days ago | Handshake completed | 141 ms |
| 17 days ago | Handshake completed | 375 ms |
| 19 days ago | Handshake completed | 241 ms |
| 20 days ago | Handshake completed | 179 ms |
| 21 days ago | Handshake completed | 143 ms |
| 22 days ago | Handshake completed | 250 ms |
| 22 days ago | Handshake completed | 48 ms |
| 23 days ago | Handshake completed | 221 ms |
| 25 days ago | Handshake completed | 243 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.