_ registry / mcp streamable-http · checked 18m ago

findmytide

https://api.findmytide.com

Registry code: d5d1218257acdacb

api record

Find My Tide predicts tides for about 4,600 stations in the United States, Canada and US territories. Find a station with search_stations, then call get_tides with its id. Times are local to the station. Every answer carries a safety notice and attribution: pass them on, and never present these predictions as suitable for navigation.

endpoint
https://api.findmytide.com/mcp
protocol
streamable-http ·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 findmytide live?
Yes — it answered the hub's last check (checked 18m ago). It answered 100% of checks over the last 30 days.
Is findmytide free to use?
Yes — the hub reached it with no key and no payment.
What tools does findmytide have?
3 tools: get_tides, get_conditions, search_stations.
Is findmytide 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
99.6%

90 days 99.1%· all time 99.1%

latency
502ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 423 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get high and low tide times
  • find tide stations by place
  • get wind and sea temperature at a station
takes → gives
text → data
tools
3 reads
_ 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 3 tools
3 never probed 0 of 3 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.

  • get_tides reads unknown 18m ago

    High and low tide times and heights for one station, over one or more days in the station's local time, plus the current height and direction when the range includes now. Times are ISO 8601 with the station's UTC offset. Heights are above the station's chart datum, in feet for US stations and metres for Canadian ones unless units is given.

    mcp-tool

    {
      "type": "object",
      "required": [
        "station_id"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "First day, YYYY-MM-DD in the station's local calendar. Defaults to today there."
        },
        "days": {
          "type": "integer",
          "default": 2,
          "maximum": 7,
          "minimum": 1
        },
        "units": {
          "enum": [
            "m",
            "ft"
          ],
          "type": "string"
        },
        "station_id": {
          "type": "string",
          "description": "From search_stations, e.g. \"noaa:9447130\"."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • get_conditions reads unknown 18m ago

    Current wind speed and direction, sea surface temperature and sky at a tide station. Any of them may be missing where the forecast service has no data.

    mcp-tool

    {
      "type": "object",
      "required": [
        "station_id"
      ],
      "properties": {
        "station_id": {
          "type": "string",
          "description": "From search_stations, e.g. \"noaa:9447130\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_stations reads unknown 18m ago

    Find tide stations in the United States, Canada and US territories by place name, by position, or both. With a name, results are ranked by how well they match (then by distance, if a position is given). With only a position, the nearest stations come first. Returns each station's id, which get_tides and get_conditions take.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "description": "A place, station or region name, e.g. \"Monterey\", \"Bay of Fundy\", \"BC\"."
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Decimal degrees."
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Decimal degrees."
        }
      },
      "additionalProperties": false
    }
    arguments 29 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 d5d1218257acdacb.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d5d1218257acdacb/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/d5d1218257acdacb/badge.svg)](https://brick.blue/agent/d5d1218257acdacb?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
70%

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.