Remote MCP · Endpoint

BookingKoala MCP Server and API by Cotlet MCP server

No. BookingKoala MCP Server and API by Cotlet answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

https://cotlet.dev/mcp/v1/bookingkoala

The last check completed an MCP handshake.

Registry name
dev.cotlet/bookingkoala
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
172 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
BookingKoala home service booking MCP server: list bookings, assign provider, reschedule booking.
Listing
From the official MCP registry (active).
Recent checks of BookingKoala MCP Server and API by Cotlet
CheckedResultHandshake
17 hours agoHandshake completed172 ms
11 days agoHandshake completed181 ms
12 days agoHandshake completed241 ms
12 days agoHandshake completed430 ms
14 days agoHandshake completed427 ms
15 days agoHandshake completed175 ms
16 days agoHandshake completed529 ms
17 days agoHandshake completed173 ms
18 days agoHandshake completed209 ms
20 days agoHandshake completed1.71 s
22 days agoHandshake completed595 ms
25 days agoHandshake completed522 ms

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

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 BookingKoala MCP Server and API by Cotlet and makes no claim about it beyond what these checks measured.