# Zovo Tide Tables (remote · tide-tables.zovo.one)

Monthly tide calendars

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `tide-tables.zovo.one`: 80/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-tide-tables/tide-tables.md), [page](https://verifymcp.io/servers/theluckystrike-tide-tables/tide-tables)

## Channel facts

- Endpoint: `https://tide-tables.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 80/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 615 tokens (~205/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% 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 2 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Tide Tables MCP server?

Zovo Tide Tables is a hosted endpoint at https://tide-tables.zovo.one/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 theluckystrike-tide-tables 'https://tide-tables.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-tide-tables": {
      "url": "https://tide-tables.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-tide-tables": {
      "type": "http",
      "url": "https://tide-tables.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-tide-tables]
url = "https://tide-tables.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-tide-tables": {
      "type": "remote",
      "url": "https://tide-tables.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-tide-tables --url 'https://tide-tables.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-tide-tables:
    url: "https://tide-tables.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-tide-tables": {
      "Transport": "http",
      "Url": "https://tide-tables.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-tide-tables -t streamable-http -u 'https://tide-tables.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-tide-tables": {
      "type": "http",
      "url": "https://tide-tables.zovo.one/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 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 74)

First indexed and scored.

## MCP tools (2)

### `find_tide_stations` (~203 tokens)

Find tide stations

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.

Input parameters:

- `limit` (integer): How many stations to return, 1 to 10. Default 5, e.g. 5.
- `place` (string, required): A US coastal city or town, a NOAA tide station name, or a NOAA station id. Add the state after a comma if you know it, e.g. Monterey, CA or Montauk or 9414290.
- `state` (string): Optional two-letter US state or territory code to narrow the search, e.g. FL.

Output parameters:

- `matched_city`
- `name_matches` (number)
- `note` (string)
- `query` (string)
- `source` (string)
- `state` (string)
- `stations` (array)

### `generate_tide_calendar` (~338 tokens)

Generate tide calendar

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.

Input parameters:

- `end_date` (string): Last day as YYYY-MM-DD (inclusive), e.g. 2027-01-05.
- `low_tide_filter` (object): Optional: highlight low tides that fit a plan such as tide pooling or clamming, e.g. {"max_height":0,"daylight_only":true}.
- `month` (string): Calendar month as YYYY-MM, e.g. 2026-12. Use this or start_date and end_date.
- `start_date` (string): First day as YYYY-MM-DD, e.g. 2026-12-20. Needs end_date; at most 31 days in total.
- `station_id` (string, required): NOAA tide station id from find_tide_stations: 7 digits, or 3 letters and 4 digits for some subordinate stations, e.g. 9414290 or TPT2799.
- `units` (string): Height units: ft (default) or m, e.g. ft.

Output parameters:

- `datum` (string)
- `days` (array)
- `days_shown` (number)
- `downloads` (object)
- `filter` (string)
- `note` (string)
- `period` (object)
- `source` (object)
- `station` (object)
- `summary` (object)
- `time_zones` (array)
- `units` (string)
- `windows` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-tide-tables/tide-tables#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 75
- 2026-11-11: 75
- 2026-11-10: 74
- 2026-11-09: 74
- 2026-11-08: 74

## Common questions

### What is the Zovo Tide Tables MCP server?

Zovo Tide Tables is an MCP server listed in the public MCP registry as io.github.theluckystrike/tide-tables. Monthly tide calendars. This page covers its hosted endpoint (https://tide-tables.zovo.one/mcp).

### Is the Zovo Tide Tables MCP server safe to use?

Zovo Tide Tables scores 80 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 Zovo Tide Tables MCP server expose?

Zovo Tide Tables exposes 2 tools: find_tide_stations, generate_tide_calendar. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.

### Does the Zovo Tide Tables MCP server require authentication?

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

### Is the Zovo Tide Tables MCP server still maintained?

Zovo Tide Tables 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 Zovo Tide Tables MCP server?

VerifyMCP ran 14 checks on Zovo Tide Tables, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://tide-tables.zovo.one/mcp
- Website: https://tide-tables.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-tide-tables/tide-tables.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-tide-tables/tide-tables/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-tide-tables/tide-tables.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-tide-tables/tide-tables
