Remote MCP · Endpoint

Hotelumo Hotel Operations MCP server

No. Hotelumo Hotel Operations answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes 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
240 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 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
59 minutes agoHandshake completed240 ms
9 days agoHandshake completed197 ms
10 days agoHandshake completed321 ms
11 days agoHandshake completed161 ms
12 days agoHandshake completed381 ms
14 days agoHandshake completed163 ms
14 days agoHandshake completed171 ms
15 days agoHandshake completed177 ms
17 days agoHandshake completed250 ms
19 days agoHandshake completed542 ms
21 days agoHandshake completed181 ms
24 days agoHandshake completed480 ms
26 days agoHandshake completed238 ms
28 days agoHandshake completed441 ms

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

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.