# Cast the Water (remote · castthewater.com)

Read-only fish stocking, waters and conditions data for US lakes from Cast the Water

- Trust score: 71/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `castthewater.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-castthewater-cast-the-water/castthewater.md), [page](https://verifymcp.io/servers/com-castthewater-cast-the-water/castthewater)

## Channel facts

- Endpoint: `https://castthewater.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 323 tokens (~80/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 9 days we've observed: 9 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
  - Structured output schemas are declared (50% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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).

## Install

### How do I install the Cast the Water MCP server?

Cast the Water is a hosted endpoint at https://castthewater.com/mcp, 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-castthewater-cast-the-water 'https://castthewater.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-castthewater-cast-the-water": {
      "url": "https://castthewater.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-castthewater-cast-the-water": {
      "type": "http",
      "url": "https://castthewater.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-castthewater-cast-the-water]
url = "https://castthewater.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-castthewater-cast-the-water": {
      "type": "remote",
      "url": "https://castthewater.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-castthewater-cast-the-water --url 'https://castthewater.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-castthewater-cast-the-water:
    url: "https://castthewater.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-castthewater-cast-the-water": {
      "Transport": "http",
      "Url": "https://castthewater.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-castthewater-cast-the-water -t streamable-http -u 'https://castthewater.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-castthewater-cast-the-water": {
      "type": "http",
      "url": "https://castthewater.com/mcp"
    }
  }
}
```

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-21 (score 71, +1)

- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [security regression] Tool “get_recent_stockings” was removed
- [security] Tool “fetch” rewrote its description, which is the text the model reads
- [security] Tool “get_water” rewrote its description, which is the text the model reads
- [functional improvement] Tool coverage: 73% → 86%
- [functional improvement] Schema quality: 427 → 323
- [functional improvement] Tool coverage: 40% → 50%

### 2026-11-17 (score 70, −6)

- [security regression] Authorization: pass → partial
- [security] The server changed its declared name: Cast the Water water bodies → Cast the Water
- [functional regression] Schema quality: 254 → 427
- [functional improvement] Tool coverage: 63% → 73%
- [functional] First check of Tool coverage: 40
- [functional] New tool “fetch”
- [functional] New tool “search”

### 2026-11-14 (score 76, +16)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [security regression] Tool “find_nearby” was removed
- [security regression] Tool “get_conditions” was removed
- [security regression] Tool “get_nearby_waterbodies” was removed
- [security regression] Tool “get_species” was removed
- [security regression] Tool “get_stocking_history” was removed
- [security regression] Tool “get_waterbody” was removed
- [security regression] Tool “search_places” was removed
- [security regression] Tool “search_waterbodies” was removed
- [security improvement] Authorization: unverified → pass
- [functional improvement] Schema quality: 942 → 254
- [functional improvement] Tool coverage: 31% → 63%
- [functional] Schema quality: fair → good

### 2026-11-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 60)

First indexed and scored.

## MCP tools (4)

### `search_waters` (~72 tokens)

Search public waters by name. Optional two-letter state. Only states open for indexing are returned, each with its castthewater.com page URL. At most 25 hits.

Input parameters:

- `query` (string, required): Water name or fragment
- `state` (string): Optional US state abbreviation. Closed states are not available.

### `get_water` (~81 tokens)

One public water by id or slug: species, fishing conditions when cached, and depth or water level when we have them, plus its castthewater.com page URL. A closed state is not available.

Input parameters:

- `slug` (string): Public slug or waters path, such as ny/essex/lake-placid
- `water_id` (string)

### `search` (~108 tokens)

Use this when you need to find a public fishing water by name for research or a citation. Optional two-letter state. Only states open for indexing are searched, at most 25 hits, each with its castthewater.com page URL. An empty query returns no results. Call fetch with an id from these results.

Input parameters:

- `query` (string, required): Water name or words to search. An empty query returns no results.
- `state` (string): Optional US state abbreviation. Closed states are left out.

Output parameters:

- `results` (array)

### `fetch` (~62 tokens)

Use this when you already have a water id from search and need the readable detail: species and a conditions summary when one is already cached. A closed state is not available. This does not fetch a live forecast.

Input parameters:

- `id` (string, required): Water id returned by search.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 70
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 60
- 2026-11-12: 60

## Common questions

### What is the Cast the Water MCP server?

Cast the Water is an MCP server listed in the public MCP registry as com.castthewater/cast-the-water. Read-only fish stocking, waters and conditions data for US lakes from Cast the Water. This page covers its hosted endpoint (https://castthewater.com/mcp).

### Is the Cast the Water MCP server safe to use?

Cast the Water scores 71 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 Cast the Water MCP server expose?

Cast the Water exposes 4 tools: search_waters, get_water, search, fetch. Their descriptions and schemas cost roughly 323 tokens of context every time the server is loaded.

### Does the Cast the Water MCP server require authentication?

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

### Is the Cast the Water MCP server still maintained?

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

### What did VerifyMCP test on the Cast the Water MCP server?

VerifyMCP ran 13 checks on Cast the Water, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://castthewater.com/mcp
- Website: https://castthewater.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-castthewater-cast-the-water/castthewater.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-castthewater-cast-the-water/castthewater/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-castthewater-cast-the-water/castthewater.json
- HTML version of this page: https://verifymcp.io/servers/com-castthewater-cast-the-water/castthewater
