Remote MCP · Endpoint

Fantasize cruise finder MCP server

No. Fantasize cruise finder answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
209 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
2 hours agoHandshake completed209 ms
3 days agoHandshake completed201 ms
12 days agoHandshake completed204 ms
13 days agoHandshake completed208 ms
14 days agoHandshake completed205 ms
15 days agoHandshake completed204 ms
16 days agoHandshake completed224 ms
17 days agoHandshake completed217 ms
18 days agoHandshake completed205 ms
19 days agoHandshake completed209 ms
22 days agoHandshake completed207 ms
25 days agoHandshake completed202 ms
27 days agoFailed - the request timed out—
29 days agoHandshake completed8.32 s

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

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.