Remote MCP · Endpoint
Appointment Booking MCP server
No. Appointment Booking answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://hatchloop.dev/mcp/appointment-booking
The last check completed an MCP handshake.
- Registry name
- dev.hatchloop/appointment-booking
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 708 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- Find real businesses and book appointments. Books via Cal.com; imports 12 platforms.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 708 ms |
| 1 day ago | Handshake completed | 666 ms |
| 2 days ago | Handshake completed | 684 ms |
| 3 days ago | Handshake completed | 685 ms |
| 4 days ago | Handshake completed | 701 ms |
| 5 days ago | Handshake completed | 811 ms |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Handshake completed | 702 ms |
| 11 days ago | Handshake completed | 887 ms |
| 14 days ago | Handshake completed | 748 ms |
| 16 days ago | Handshake completed | 768 ms |
| 18 days ago | Handshake completed | 734 ms |
| 20 days ago | Handshake completed | 719 ms |
| 22 days ago | Handshake completed | 732 ms |
| 24 days ago | Handshake completed | 726 ms |
| 26 days ago | Handshake completed | 716 ms |
| 27 days ago | Handshake completed | 731 ms |
| 28 days ago | Handshake completed | 722 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.
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 Appointment Booking and makes no claim about it beyond what these checks measured.