Remote MCP · Endpoint

Dream On Concierge MCP server

No. Dream On Concierge answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://dreamonsail.com/mcp

The last check completed an MCP handshake.

Registry name
com.dreamonsail/concierge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
247 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Luxury crewed catamaran charter in the BVI: availability, published-rate quotes and hold requests.
Listing
From the official MCP registry (active).
Recent checks of Dream On Concierge
CheckedResultHandshake
4 hours agoHandshake completed247 ms
10 days agoHandshake completed265 ms
11 days agoHandshake completed239 ms
11 days agoHandshake completed265 ms
13 days agoHandshake completed254 ms
14 days agoHandshake completed303 ms
15 days agoHandshake completed328 ms
16 days agoHandshake completed319 ms
17 days agoHandshake completed344 ms
19 days agoHandshake completed208 ms
22 days agoHandshake completed267 ms
24 days agoHandshake completed264 ms
26 days agoHandshake completed276 ms
29 days agoHandshake completed431 ms

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

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 Dream On Concierge and makes no claim about it beyond what these checks measured.