Remote MCP · Endpoint
HasData Booking.com MCP server
No. HasData Booking.com answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.hasdata.com/mcp?apis=booking
The last check completed an MCP handshake.
- Registry name
- com.hasdata/booking
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 119 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Booking.com stays by destination and dates, and full property details, as structured JSON.
- Repository
- https://github.com/HasData/booking-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 119 ms |
| 19 hours ago | Handshake completed | 151 ms |
| 2 days ago | Handshake completed | 125 ms |
| 3 days ago | Handshake completed | 132 ms |
| 4 days ago | Handshake completed | 201 ms |
| 5 days ago | Handshake completed | 126 ms |
| 6 days ago | Handshake completed | 125 ms |
| 7 days ago | Handshake completed | 126 ms |
| 10 days ago | Handshake completed | 127 ms |
| 13 days ago | Handshake completed | 627 ms |
| 15 days ago | Handshake completed | 265 ms |
| 17 days ago | Handshake completed | 138 ms |
| 19 days ago | Handshake completed | 792 ms |
| 21 days ago | Handshake completed | 128 ms |
| 23 days ago | Handshake completed | 136 ms |
| 25 days ago | Handshake completed | 124 ms |
| 27 days ago | Handshake completed | 164 ms |
| 28 days ago | Handshake completed | 143 ms |
| 29 days ago | Handshake completed | 712 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 HasData Booking.com and makes no claim about it beyond what these checks measured.