Remote MCP · Endpoint

OKstays MCP server

No. OKstays answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://okstays.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.okstays/okstays
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
204 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hotels ranked by real comfort, not commission: efficient AC, comfy beds, soundproof rooms and more
Listing
From the official MCP registry (active).
Recent checks of OKstays
CheckedResultHandshake
18 minutes agoHandshake completed204 ms
9 days agoHandshake completed223 ms
9 days agoHandshake completed743 ms
11 days agoHandshake completed132 ms
12 days agoHandshake completed328 ms
13 days agoHandshake completed157 ms
14 days agoHandshake completed196 ms
14 days agoHandshake completed155 ms
16 days agoHandshake completed198 ms
19 days agoHandshake completed515 ms
21 days agoHandshake completed148 ms
24 days agoHandshake completed547 ms
26 days agoHandshake completed219 ms

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

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