Remote MCP · Endpoint

Premium cruise fares MCP server

No. Premium cruise fares answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://luxuryforless.cruises/mcp

The last check completed an MCP handshake.

Registry name
cruises.luxuryforless/premium-cruise-fares
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
359 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search premium cruise fares by line, ship, nights, date, and rate.
Listing
From the official MCP registry (active).
Recent checks of Premium cruise fares
CheckedResultHandshake
20 minutes agoHandshake completed359 ms
9 days agoHandshake completed202 ms
9 days agoHandshake completed219 ms
11 days agoHandshake completed169 ms
12 days agoHandshake completed103 ms
13 days agoHandshake completed298 ms
14 days agoHandshake completed223 ms
15 days agoHandshake completed232 ms
16 days agoHandshake completed58 ms
19 days agoHandshake completed211 ms
21 days agoHandshake completed179 ms
24 days agoHandshake completed786 ms
26 days agoHandshake completed320 ms
28 days agoHandshake completed184 ms

The last 14 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 Premium cruise fares and makes no claim about it beyond what these checks measured.