Remote MCP · Endpoint
io.usefulapi/acuity-scheduling MCP server
No. io.usefulapi/acuity-scheduling answered an MCP handshake 21 minutes ago.
UpLast checked 21 minutes 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
- 143 ms
- Tools exposed
- 18 tools
- Uptime, last 30 days
- 100% from 5 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 |
|---|---|---|
| 21 minutes ago | Handshake completed | 143 ms |
| 1 day ago | Handshake completed | 250 ms |
| 1 day ago | Handshake completed | 48 ms |
| 2 days ago | Handshake completed | 221 ms |
| 3 days ago | Handshake completed | 243 ms |
The last 5 checks. Full history is kept for 30 days; the all-time counter stands at 5 responding of 5.
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 io.usefulapi/acuity-scheduling and makes no claim about it beyond what these checks measured.