Connect Find My Tide and your agent gets 3 tools, among them get_conditions, get_tides, search_stations. It answers at https://api.findmytide.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 7 November 2026, succeeded.
Tide times and heights for about 4,600 US and Canadian stations. Not for navigation.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_conditions | 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. Inputs: station_id |
get_tides | 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 t Inputs: station_id, date, days, units |
search_stations | 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 sta Inputs: query, latitude, longitude, limit |
Every block below points at https://api.findmytide.com/mcp. Pick your client and copy.
claude mcp add --transport http find-my-tide https://api.findmytide.com/mcp
{
"mcpServers": {
"find-my-tide": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.findmytide.com/mcp"]
}
}
}{
"mcpServers": {
"find-my-tide": {
"url": "https://api.findmytide.com/mcp"
}
}
}{
"servers": {
"find-my-tide": {
"type": "http",
"url": "https://api.findmytide.com/mcp"
}
}
}{
"context_servers": {
"find-my-tide": {
"url": "https://api.findmytide.com/mcp"
}
}
}{
"mcpServers": {
"find-my-tide": {
"serverUrl": "https://api.findmytide.com/mcp"
}
}
}{
"mcpServers": {
"find-my-tide": {
"url": "https://api.findmytide.com/mcp"
}
}
}name: Find My Tide
version: 0.0.1
schema: v1
mcpServers:
- name: Find My Tide
type: streamable-http
url: https://api.findmytide.com/mcp{
"mcpServers": {
"find-my-tide": {
"httpUrl": "https://api.findmytide.com/mcp"
}
}
}{
"mcpServers": {
"find-my-tide": {
"type": "http",
"url": "https://api.findmytide.com/mcp"
}
}
}{
"mcpServers": {
"find-my-tide": {
"url": "https://api.findmytide.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.findmytide.com%2Fmcp&type=streamable_http&id=find-my-tide&name=Find%20My%20Tide
It answered our last check on 7 November 2026 in 103 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by findmytide.com and served from api.findmytide.com, the vendor's own domain: https://api.findmytide.com/mcp.
3, as returned by the server's own tools/list on 13 November 2026: get_conditions, get_tides, search_stations.
It answered our last check on 7 November 2026 in 103 ms. Over 4 checks since 23 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.findmytide.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.findmytide. Endpoint host: api.findmytide.com. ARD identifier: urn:air:com.findmytide:mcp:tides.
First indexed 23 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.