Remote MCP · Endpoint

Gaplessly Booking MCP server

No. Gaplessly Booking answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gaplessly.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.gaplessly/booking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
544 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find free times at Gaplessly businesses on a plan with AI booking, then get a link to book.
Listing
From the official MCP registry (active).
Recent checks of Gaplessly Booking
CheckedResultHandshake
1 hour agoHandshake completed544 ms
2 days agoHandshake completed315 ms
4 days agoHandshake completed575 ms
6 days agoHandshake completed520 ms
8 days agoHandshake completed563 ms
10 days agoHandshake completed339 ms
12 days agoHandshake completed530 ms
14 days agoHandshake completed2.12 s
16 days agoHandshake completed310 ms
17 days agoHandshake completed2.12 s
18 days agoHandshake completed364 ms
21 days agoHandshake completed317 ms
22 days agoHandshake completed540 ms
24 days agoHandshake completed837 ms

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

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 Gaplessly Booking and makes no claim about it beyond what these checks measured.