# KaiCast Ocean Conditions (remote · kaicast.com)

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

- Trust score: 88/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `kaicast.com`: 88/100 (this document), [markdown](https://verifymcp.io/servers/com-kaicast-ocean-conditions/kaicast.md), [page](https://verifymcp.io/servers/com-kaicast-ocean-conditions/kaicast)

## Channel facts

- Endpoint: `https://kaicast.com/mcp?ref=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## 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.

### Claude

```bash
claude mcp add --transport http com-kaicast-ocean-conditions 'https://kaicast.com/mcp?ref=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kaicast-ocean-conditions": {
      "url": "https://kaicast.com/mcp?ref=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kaicast-ocean-conditions": {
      "type": "http",
      "url": "https://kaicast.com/mcp?ref=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kaicast-ocean-conditions]
url = "https://kaicast.com/mcp?ref=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-kaicast-ocean-conditions": {
      "type": "remote",
      "url": "https://kaicast.com/mcp?ref=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-kaicast-ocean-conditions --url 'https://kaicast.com/mcp?ref=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kaicast-ocean-conditions:
    url: "https://kaicast.com/mcp?ref=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kaicast-ocean-conditions": {
      "Transport": "http",
      "Url": "https://kaicast.com/mcp?ref=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kaicast-ocean-conditions -t streamable-http -u 'https://kaicast.com/mcp?ref=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "com-kaicast-ocean-conditions": {
      "type": "http",
      "url": "https://kaicast.com/mcp?ref=mcp-registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 88, +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.

### 2026-11-03 (score 87, +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.

### 2026-11-01 (score 86, +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.

### 2026-10-30 (score 85, +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.

### 2026-10-29 (score 84, 0)

- [functional regression] Schema quality: 955 → 1437
- [functional] New tool “best_months”
- [functional] New tool “get_seasonality”

### 2026-10-27 (score 84, +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.

### 2026-10-25 (score 83, +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.

### 2026-10-23 (score 82, +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.

## MCP tools (6)

### `get_conditions` (~187 tokens)

Get ocean conditions

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.

Input parameters:

- `from` (string): First day, spot-local YYYY-MM-DD. Default: today.
- `lat` (number): Latitude; snaps to the nearest covered spot within 30 km.
- `lon` (number): Longitude; use with lat.
- `spot` (string): Spot id, e.g. "electric-beach". Pass this OR lat+lon.
- `to` (string): Last day, inclusive. At most 7 days after from. Default: from + 6.

Output parameters:

- `periods` (array)
- `schema` (string)
- `source` (object)
- `spot` (object)

### `list_coverage` (~68 tokens)

List KaiCast coverage

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.

Input parameters:

- `region` (string): Limit to one region id.

Output parameters:

- `regions` (array)
- `schema` (string)
- `source` (object)

### `recommend_spot` (~290 tokens)

Recommend spots

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.

Input parameters:

- `activity` (string, required): What the user wants to do.
- `date` (string): Spot-local day to plan for. Default: today, or tomorrow once today's daylight has passed. Up to 6 days ahead.
- `lat` (number): Latitude, decimal degrees. Use with lon.
- `limit` (integer): How many picks (default 3, max 5).
- `lon` (number): Longitude, decimal degrees. Use with lat.
- `radius_km` (number): Search radius around lat/lon in km (default 40, max 100).
- `region` (string): Region id, e.g. "us-hi-oahu".
- `spot` (string): Spot id, e.g. "hanauma-bay".

Output parameters:

- `coverage` (object)
- `disclaimer` (string)
- `message`
- `picks` (array)
- `schema` (string)
- `source` (object)
- `status` (string)

### `best_day` (~219 tokens)

Find the best day

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.

Input parameters:

- `activity` (string, required): What the user wants to do.
- `from` (string): Window start, spot-local. Default: today.
- `lat` (number): Latitude, decimal degrees. Use with lon.
- `lon` (number): Longitude, decimal degrees. Use with lat.
- `radius_km` (number): Search radius around lat/lon in km (default 40, max 100).
- `region` (string): Region id, e.g. "us-hi-oahu".
- `spot` (string): Spot id, e.g. "hanauma-bay".
- `to` (string): Window end, inclusive, at most 7 days. Default: from + 6.

Output parameters:

- `best`
- `coverage` (object)
- `days` (array)
- `disclaimer` (string)
- `message`
- `schema` (string)
- `source` (object)
- `status` (string)

### `get_seasonality` (~256 tokens)

Get seasonality (trip planning)

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.

Input parameters:

- `area` (string): Trip-planning area id, e.g. "us-hi-oahu".
- `lat` (number): Latitude; resolves to the nearest covered area within 50 km. Use with lon.
- `lon` (number): Longitude; use with lat.
- `month_from` (integer): First month, 1-12. Default: all 12 months.
- `month_to` (integer): Last month, 1-12, inclusive; wraps the year (11 to 2 = Nov-Feb).
- `spot` (string): Spot id; resolves to the area containing it.

Output parameters:

- `area` (object)
- `months` (array)
- `notice` (string)
- `schema` (string)
- `source` (object)

### `best_months` (~226 tokens)

Best months for an activity or species

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.

Input parameters:

- `area` (string): Trip-planning area id, e.g. "us-hi-oahu".
- `for` (string, required): What to plan for: an activity (dive, snorkel, freedive, whale_swim), a species word (e.g. "manta", "whale shark"), or calm / warm / clear.
- `lat` (number): Latitude; resolves to the nearest covered area within 50 km. Use with lon.
- `limit` (integer): How many months (default 3).
- `lon` (number): Longitude; use with lat.
- `spot` (string): Spot id; resolves to the area containing it.

Output parameters:

- `area` (object)
- `basis` (string)
- `for` (string)
- `months` (array)
- `schema` (string)
- `source` (object)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-kaicast-ocean-conditions/kaicast#diagnostics

## Score history

- 2026-11-05: 88
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 84
- 2026-10-28: 84
- 2026-10-27: 84
- 2026-10-26: 83
- 2026-10-25: 83
- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-11: 76
- 2026-10-10: 76
- 2026-10-09: 75
- 2026-10-07: 74

## 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.

## Links

- Remote endpoint: https://kaicast.com/mcp?ref=mcp-registry
- Website: https://kaicast.com/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-kaicast-ocean-conditions/kaicast.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kaicast-ocean-conditions/kaicast.json
- HTML version of this page: https://verifymcp.io/servers/com-kaicast-ocean-conditions/kaicast