Remote MCP · Endpoint

Bluerails Hotels MCP server

No. Bluerails Hotels answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://402.bluerails.com/mcp

The last check completed an MCP handshake.

Registry name
com.bluerails/hotels
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
255 ms
Tools exposed
2 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Live hotel search and booking for AI agents in DACH, the UK and 10 US cities.
Listing
From the official MCP registry (active).
Recent checks of Bluerails Hotels
CheckedResultHandshake
8 hours agoHandshake completed255 ms
10 days agoHandshake completed268 ms
11 days agoHandshake completed458 ms

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

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