Remote MCP · Endpoint

Staylist World MCP server

No. Staylist World answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://staylist.world/mcp

The last check completed an MCP handshake.

Registry name
world.staylist/staylist
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
729 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free hotel comparison for AI assistants: 77k hotels on the same criteria, with reasons. No key.
Listing
From the official MCP registry (active).
Recent checks of Staylist World
CheckedResultHandshake
1 hour agoHandshake completed729 ms
2 days agoHandshake completed970 ms
4 days agoHandshake completed341 ms
6 days agoHandshake completed680 ms
8 days agoHandshake completed1.29 s
10 days agoHandshake completed317 ms
12 days agoHandshake completed746 ms
14 days agoHandshake completed347 ms
16 days agoHandshake completed784 ms
17 days agoHandshake completed925 ms
18 days agoHandshake completed803 ms
21 days agoHandshake completed518 ms
22 days agoHandshake completed396 ms
24 days agoHandshake completed646 ms

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

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