Remote MCP · Endpoint

GuruHotel MCP server

No. GuruHotel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://guruhotel.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.guruhotel/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
88 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
GuruHotel product knowledge: direct booking platform for hotels, PMS compatibility and pricing.
Listing
From the official MCP registry (active).
Recent checks of GuruHotel
CheckedResultHandshake
1 hour agoHandshake completed88 ms
2 days agoHandshake completed94 ms
4 days agoHandshake completed74 ms
5 days agoHandshake completed173 ms
7 days agoHandshake completed71 ms
8 days agoHandshake completed75 ms
9 days agoHandshake completed892 ms
12 days agoHandshake completed92 ms
13 days agoHandshake completed215 ms
15 days agoHandshake completed135 ms
16 days agoHandshake completed69 ms
17 days agoHandshake completed97 ms
18 days agoHandshake completed80 ms
19 days agoHandshake completed64 ms
20 days agoHandshake completed86 ms
21 days agoHandshake completed142 ms
22 days agoHandshake completed79 ms

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

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