Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KaiCast Ocean Conditions

REMOTE · KAICAST.COM

Ocean conditions by location: water visibility, swell, wind, tide, plus dive and snorkel spot picks.

Available components

+4 this week 88 Trust /100

Last scanned (11 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1437 tokens (~205/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 0
    • Schema quality: 955 → 1437 ▼ functional
    • New tool “best_months” functional
    • New tool “get_seasonality” functional
  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://kaicast.com/mcp?ref=mcp-registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kaicast.com CN=WR3,O=Google Trust Services,C=US 11 Sept 2026 11 Dec 2026 RSA 2048 SHA256-RSA 14939c0078a83dba0a27d8ac114bd985
SANs: kaicast.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of kaicast.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
kaicast.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(self), camera=(), microphone=(self), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kaicast.com/mcp?ref=mcp-registry Verified 200
http (plaintext) http://kaicast.com/mcp?ref=mcp-registry HTTPS enforced 301 https://kaicast.com/mcp?ref=mcp-registry
MCP tools · 6 exposed · ~1,246 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
best_day ~219

Which day in a window (max 7 days) is best for an activity at a destination — a spot, a region, or lat+lon with a radius — and why, versus the runner-up. Returns every day's best score, confidence, caveats and a KaiCast spot card for the winner. Free during early access.

NameTypeReqDescription
activitystringyesWhat the user wants to do.
fromstring–Window start, spot-local. Default: today.
latnumber–Latitude, decimal degrees. Use with lon.
lonnumber–Longitude, decimal degrees. Use with lat.
radius_kmnumber–Search radius around lat/lon in km (default 40, max 100).
regionstring–Region id, e.g. "us-hi-oahu".
spotstring–Spot id, e.g. "hanauma-bay".
tostring–Window end, inclusive, at most 7 days. Default: from + 6.
NameTypeReqDescription
best–––
coverageobjectyes–
daysarray––
disclaimerstringyes–
message–––
schemastringyes–
sourceobjectyes–
statusstringyes–

No examples provided.

best_months ~226

Ranks the calendar months for one thing at one place: an activity (dive, snorkel, freedive, whale_swim), a species (e.g. manta, whale shark), or calm seas / warm water / clear water. Says whether the ranking comes from multi-year data or curated research seasons, with confidence and caveats. A decision call: metered, free during early access.

NameTypeReqDescription
areastring–Trip-planning area id, e.g. "us-hi-oahu".
forstringyesWhat to plan for: an activity (dive, snorkel, freedive, whale_swim), a species word (e.g. "manta", "whale shark"), or calm / warm / clear.
latnumber–Latitude; resolves to the nearest covered area within 50 km. Use with lon.
limitinteger–How many months (default 3).
lonnumber–Longitude; use with lat.
spotstring–Spot id; resolves to the area containing it.
NameTypeReqDescription
areaobjectyes–
basisstringyes–
forstringyes–
monthsarrayyes–
schemastringyes–
sourceobjectyes–
statusstringyes–

No examples provided.

get_conditions ~187

Facts for ONE covered spot over up to 7 days: 3-hour forecast periods with condition score (0-100) and rating, water visibility (ft), swell height/period/direction, wind, tide state and height, water temperature, plus tide events and data quality. Pass a spot id, or lat+lon to use the nearest covered spot within 30 km. Free.

NameTypeReqDescription
fromstring–First day, spot-local YYYY-MM-DD. Default: today.
latnumber–Latitude; snaps to the nearest covered spot within 30 km.
lonnumber–Longitude; use with lat.
spotstring–Spot id, e.g. "electric-beach". Pass this OR lat+lon.
tostring–Last day, inclusive. At most 7 days after from. Default: from + 6.
NameTypeReqDescription
periodsarrayyes–
schemastringyes–
sourceobjectyes–
spotobjectyes–

No examples provided.

get_seasonality ~256

What a place is usually like in a given month, for trip planning months ahead: per month, sea-surface temperature (p10/p50/p90 °C), wave height (p50/p90 m), wind (p50/p90 m/s), share of rough days, model water visibility (p25/p50/p75 m, low confidence), tropical-cyclone frequency, wildlife seasons, access rules and best activities. Every field carries its sources; curated seasons are drafts pending local review. Pass an area id, a spot id, or lat+lon, and optionally a month range. Free.

NameTypeReqDescription
areastring–Trip-planning area id, e.g. "us-hi-oahu".
latnumber–Latitude; resolves to the nearest covered area within 50 km. Use with lon.
lonnumber–Longitude; use with lat.
month_frominteger–First month, 1-12. Default: all 12 months.
month_tointeger–Last month, 1-12, inclusive; wraps the year (11 to 2 = Nov-Feb).
spotstring–Spot id; resolves to the area containing it.
NameTypeReqDescription
areaobjectyes–
monthsarrayyes–
noticestringyes–
schemastringyes–
sourceobjectyes–

No examples provided.

list_coverage ~68

Which regions and spots KaiCast covers, and whether each region supports ranked decisions (spot picks and best-day answers) or facts only. Also lists supported activities and how directly each is modeled. Anywhere not listed is not covered. Free.

NameTypeReqDescription
regionstring–Limit to one region id.
NameTypeReqDescription
regionsarrayyes–
schemastringyes–
sourceobjectyes–

No examples provided.

recommend_spot ~290

Ranked top picks (max 5) for an activity in one area on one day — by region id, or lat+lon with a radius. Each pick has the best daylight window, why (from the published conditions), a confidence score with its factors, caveats, and a KaiCast spot card. Returns status "not_covered" / "conditions_only" / "activity_not_modeled" honestly instead of guessing. Activities: snorkel (native model), dive, freedive, spearfish (proxy model; spots in water closed to spearfishing are excluded), surf (not modeled). Free during early access.

NameTypeReqDescription
activitystringyesWhat the user wants to do.
datestring–Spot-local day to plan for. Default: today, or tomorrow once today's daylight has passed. Up to 6 days ahead.
latnumber–Latitude, decimal degrees. Use with lon.
limitinteger–How many picks (default 3, max 5).
lonnumber–Longitude, decimal degrees. Use with lat.
radius_kmnumber–Search radius around lat/lon in km (default 40, max 100).
regionstring–Region id, e.g. "us-hi-oahu".
spotstring–Spot id, e.g. "hanauma-bay".
NameTypeReqDescription
coverageobjectyes–
disclaimerstringyes–
message–––
picksarrayyes–
schemastringyes–
sourceobjectyes–
statusstringyes–

No examples provided.

Install

How do I install the KaiCast Ocean Conditions MCP server?

KaiCast Ocean Conditions is a hosted endpoint at https://kaicast.com/mcp?ref=mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · kaicast.com

# add to Claude Code
claude mcp add --transport http com-kaicast-ocean-conditions 'https://kaicast.com/mcp?ref=mcp-registry'
Common questions

What is the KaiCast Ocean Conditions MCP server?

KaiCast Ocean Conditions is an MCP server listed in the public MCP registry as com.kaicast/ocean-conditions. Ocean conditions by location: water visibility, swell, wind, tide, plus dive and snorkel spot picks. This page covers its hosted endpoint (https://kaicast.com/mcp?ref=mcp-registry).

Is the KaiCast Ocean Conditions MCP server safe to use?

KaiCast Ocean Conditions scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the KaiCast Ocean Conditions MCP server expose?

KaiCast Ocean Conditions exposes 6 tools: get_conditions, list_coverage, recommend_spot, best_day, get_seasonality, best_months. Their descriptions and schemas cost roughly 1,246 tokens of context every time the server is loaded.

Does the KaiCast Ocean Conditions MCP server require authentication?

No. We connected to KaiCast Ocean Conditions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the KaiCast Ocean Conditions MCP server still maintained?

KaiCast Ocean Conditions is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.