Remote MCP · Endpoint

Fantasize cruise finder MCP server

No. Fantasize cruise finder answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fantasize.net/mcp

The last check completed an MCP handshake.

Registry name
net.fantasize/cruise-finder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
207 ms
Tools exposed
10 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Find the best-value cruise: 23 lines, ~30k sailings priced nightly, low/high vs usual, book link.
Listing
From the official MCP registry (active).
Recent checks of Fantasize cruise finder
CheckedResultHandshake
1 hour agoHandshake completed207 ms
2 days agoHandshake completed202 ms
5 days agoFailed - the request timed out—
7 days agoHandshake completed8.32 s
9 days agoHandshake completed224 ms
11 days agoHandshake completed217 ms
13 days agoHandshake completed201 ms
15 days agoHandshake completed196 ms
17 days agoHandshake completed244 ms
18 days agoHandshake completed256 ms
19 days agoHandshake completed220 ms
20 days agoHandshake completed198 ms
23 days agoHandshake completed196 ms
24 days agoHandshake completed211 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Fantasize cruise finder and makes no claim about it beyond what these checks measured.