Remote MCP · Endpoint

KaiCast Ocean Conditions MCP server

No. KaiCast Ocean Conditions answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://kaicast.com/mcp?ref=mcp-registry

The last check completed an MCP handshake.

Registry name
com.kaicast/ocean-conditions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
421 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Ocean conditions by location: water visibility, swell, wind, tide, plus dive and snorkel spot picks.
Listing
From the official MCP registry (active).
Recent checks of KaiCast Ocean Conditions
CheckedResultHandshake
39 minutes agoHandshake completed421 ms
3 days agoHandshake completed391 ms
13 days agoHandshake completed462 ms
13 days agoHandshake completed556 ms
15 days agoHandshake completed366 ms
16 days agoHandshake completed255 ms
17 days agoHandshake completed375 ms
18 days agoHandshake completed278 ms
18 days agoHandshake completed259 ms
20 days agoHandshake completed509 ms
22 days agoHandshake completed423 ms
25 days agoHandshake completed353 ms
27 days agoHandshake completed968 ms
29 days agoHandshake completed346 ms

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

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 KaiCast Ocean Conditions and makes no claim about it beyond what these checks measured.