Zovo Tide Tables MCP server
io.github.theluckystrike/tide-tablestheluckystrikestreamable-httpv1.0.0Scanned
Monthly tide calendars
2 tools: 1 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Zovo Tide Tables MCP server can do
The Zovo Tide Tables MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (1 tool: generate_tide_calendar), but cannot delete data. 1 tool only reads.
1 tool reads private data (find_tide_stations); 1 tool brings in text other people can write (generate_tide_calendar).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
generate_tide_calendarUse this when the user wants a tide table, tide calendar or tide times for a NOAA station for a month or up to 31 days: high and low times and heights (MLLW, ft or m, local time), …Reads text others write1 finding
Why it is in this group
- The name "generate_tide_calendar" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "generate_tide_calendar" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "generate_tide_calendar" says "generate": a word for a change.
Description, as the server wrote it Use this when the user wants a tide table, tide calendar or tide times for a NOAA station for a month or up to 31 days: high and low times and heights (MLLW, ft or m, local time), sunrise and sunset, an optional low-tide filter, a printable PDF calendar (Letter and A4), CSV and ICS calendar files. Data is NOAA CO-OPS predictions (fetched from NOAA, cached up to 24 hours), not observations. Needs a NOAA station id (get one from find_tide_stations). Does not give currents, surf, weather or observed water levels.
Annotations the server declares
- title: Generate tide calendar
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
Only reads 1Show 1 read-only tool
find_tide_stationsUse this when the user names a US coastal place and needs the NOAA tide prediction station to use for a tide table.Reads private dataNo findings
Why it is in this group
- The name "find_tide_stations" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it Use this when the user names a US coastal place and needs the NOAA tide prediction station to use for a tide table. Takes a city or town (US places of about 15,000 people or more), a station name, or a NOAA station id, and returns the nearest stations with distance in miles. Does not return tide times; use generate_tide_calendar for those. Does not cover places outside the NOAA CO-OPS station list.
Annotations the server declares
- title: Find tide stations
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:24 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tide-tables.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including generate_tide_calendar (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "generate_tide_calendar" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "generate_tide_calendar" says "generate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http tide-tables https://tide-tables.zovo.one/mcpclaude mcp add --transport http tide-tables https://tide-tables.zovo.one/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tide-tables__find_tide_stations"
],
"ask": [
"mcp__tide-tables__generate_tide_calendar"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tide-tables. Review it before you use it.
Capability tags behind 2 rules
- mcp__tide-tables__find_tide_stations private-data
- mcp__tide-tables__generate_tide_calendar untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/tide-tables/verify?hash=fcf12729f80ee5f812a2dbea40f18bd20e5db78658b5c90abd36c2c35b411303" | jq -e '.changed == false'Pinned hash fcf12729f80e, from Nov 8, 2026, 02:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/tide-tables/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/tide-tables)Source: MCP Registry. Synced Nov 8, 2026, 03:18 UTC.
Zovo Tide Tables MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Zovo Tide Tables MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Zovo Tide Tables MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Zovo Tide Tables MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Zovo Tide Tables MCP server have?
- 2 tools: 1 write, 1 read. generate_tide_calendar and find_tide_stations.
Does the Zovo Tide Tables MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Zovo Tide Tables MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Zovo Tide Tables MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.