_ registry / mcp http-sse · checked 14h ago

Cast the Water

https://castthewater.com

Registry code: 1a1d370e2f9f1298

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://castthewater.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Cast the Water live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is Cast the Water free to use?
Yes — the hub reached it with no key and no payment.
What tools does Cast the Water have?
4 tools: search_waters, search, fetch, get_water.
Is Cast the Water safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
348ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_waters unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Water name or fragment"
        },
        "state": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Optional US state abbreviation. Closed states are not available."
        }
      }
    }
    arguments 21 lines
  • search unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 80,
          "description": "Water name or words to search. An empty query returns no results."
        },
        "state": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Optional US state abbreviation. Closed states are left out."
        }
      }
    }
    arguments 20 lines
  • fetch unknown 41h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Water id returned by search."
        }
      }
    }
    arguments 15 lines
  • get_water unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 180,
          "minLength": 1,
          "description": "Public slug or waters path, such as ny/essex/lake-placid"
        },
        "water_id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1
        }
      }
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1a1d370e2f9f1298.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1a1d370e2f9f1298/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1a1d370e2f9f1298/badge.svg)](https://brick.blue/agent/1a1d370e2f9f1298?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.