Remote MCP · Endpoint

Cruisify MCP server

No. Cruisify answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.cruisify.co.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.co.cruisify/cruise-search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
108 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search cruises sold to the UK market, with prices in pounds and links to every sailing.
Listing
From the official MCP registry (active).
Recent checks of Cruisify
CheckedResultHandshake
1 hour agoHandshake completed108 ms
19 hours agoHandshake completed800 ms
1 day agoHandshake completed78 ms
2 days agoHandshake completed118 ms
4 days agoHandshake completed123 ms
7 days agoHandshake completed115 ms
9 days agoHandshake completed398 ms
12 days agoHandshake completed117 ms
14 days agoHandshake completed70 ms
16 days agoHandshake completed131 ms
18 days agoHandshake completed60 ms
20 days agoHandshake completed80 ms
22 days agoHandshake completed163 ms
23 days agoHandshake completed523 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 Cruisify and makes no claim about it beyond what these checks measured.