Remote MCP · Endpoint

Stay Perks MCP server

No. Stay Perks answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://staysperks.com/mcp

The last check completed an MCP handshake.

Registry name
com.staysperks/stay-perks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Virtuoso luxury hotels with perks included: search 2,000+, get a quote, book. Pay hotels directly.
Listing
From the official MCP registry (active).
Recent checks of Stay Perks
CheckedResultHandshake
3 hours agoHandshake completed67 ms
3 days agoHandshake completed81 ms
13 days agoHandshake completed79 ms
14 days agoHandshake completed78 ms
15 days agoHandshake completed66 ms
16 days agoHandshake completed128 ms
18 days agoHandshake completed148 ms
18 days agoHandshake completed83 ms
19 days agoHandshake completed62 ms
21 days agoHandshake completed179 ms
22 days agoHandshake completed69 ms
25 days agoHandshake completed208 ms
27 days agoHandshake completed309 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 Stay Perks and makes no claim about it beyond what these checks measured.