Remote MCP · Endpoint

Hotelumo Hotel Operations MCP server

No. Hotelumo Hotel Operations answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.hotelumo.com/mcp

The last check completed an MCP handshake.

Registry name
com.hotelumo/hotelumo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
441 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
See your hotel's room availability, rates, housekeeping and upcoming arrivals and departures.
Listing
From the official MCP registry (active).
Recent checks of Hotelumo Hotel Operations
CheckedResultHandshake
2 hours agoHandshake completed441 ms
2 days agoHandshake completed179 ms
4 days agoHandshake completed205 ms
6 days agoHandshake completed418 ms
8 days agoHandshake completed166 ms
9 days agoHandshake completed198 ms
11 days agoHandshake completed365 ms
11 days agoHandshake completed403 ms
14 days agoHandshake completed137 ms
15 days agoHandshake completed1.39 s
17 days agoHandshake completed175 ms
19 days agoHandshake completed462 ms
20 days agoHandshake completed363 ms
21 days agoHandshake completed527 ms
22 days agoHandshake completed198 ms

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

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