# TidesAtlas (remote · tidesatlas.com)

Worldwide tide times and heights, marine weather, sea temperature, sun and moon for 13,000+ ports.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `tidesatlas.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-tidesatlas-tides/tidesatlas.md), [page](https://verifymcp.io/servers/com-tidesatlas-tides/tidesatlas)

## Channel facts

- Endpoint: `https://tidesatlas.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## 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-05.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 917 tokens (~91/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the TidesAtlas MCP server?

TidesAtlas is a hosted endpoint at https://tidesatlas.com/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 com-tidesatlas-tides 'https://tidesatlas.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-tidesatlas-tides": {
      "url": "https://tidesatlas.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-tidesatlas-tides": {
      "type": "http",
      "url": "https://tidesatlas.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-tidesatlas-tides]
url = "https://tidesatlas.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tidesatlas-tides": {
      "type": "remote",
      "url": "https://tidesatlas.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tidesatlas-tides --url 'https://tidesatlas.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-tidesatlas-tides:
    url: "https://tidesatlas.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-tidesatlas-tides": {
      "Transport": "http",
      "Url": "https://tidesatlas.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tidesatlas-tides -t streamable-http -u 'https://tidesatlas.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-tidesatlas-tides": {
      "type": "http",
      "url": "https://tidesatlas.com/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-05 (score 70, +1)

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

### 2026-11-04 (score 69, +7)

- [security improvement] Authorization: unverified → partial
- [security] Tool “get_tides” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 62)

First indexed and scored.

## MCP tools (10)

### `get_tides` (~207 tokens)

Get tide predictions (high/low water times and heights) for a port or coordinates. Returns extremes with datetime, height in meters, and type (high/low). Supports 13,000+ stations in 180 countries.

Input parameters:

- `date` (string): Start date in YYYY-MM-DD format (default: today).
- `datum` (string): Vertical datum: LAT, MSL, MLLW, MHW, MLW, MHHW, MTL, HAT (default: native datum of station).
- `days` (integer): Number of days, 1-14 (default: 1).
- `lat` (number): Latitude (-90 to 90). Alternative to port — finds the nearest station.
- `lon` (number): Longitude (-180 to 180). Must be used with lat.
- `port` (string): Station slug, e.g. "aberdeen" or "san-francisco". Use search_ports to find slugs.

### `search_ports` (~88 tokens)

Search for tide stations by name or country. Returns port name, slug, coordinates, timezone, country.

Input parameters:

- `country` (string): Filter by country slug, e.g. "united-kingdom" or "france".
- `limit` (integer): Max results, 1-500 (default: 50).
- `search` (string): Search by station name (partial match).

### `list_countries` (~27 tokens)

List all 188 countries that have tide stations, with their station counts and ISO codes.

### `get_weather` (~78 tokens)

Get weather forecast (temperature, wind, precipitation, UV, conditions) for a port or coordinates. Returns hourly and daily data.

Input parameters:

- `days` (integer): Forecast days, 1-7 (default: 3).
- `lat` (number): Latitude.
- `lon` (number): Longitude.
- `port` (string): Station slug.

### `get_marine` (~76 tokens)

Get ocean and wave forecast (wave height, swell, sea state on Douglas scale). Returns hourly and daily data.

Input parameters:

- `days` (integer): Forecast days, 1-7 (default: 3).
- `lat` (number): Latitude.
- `lon` (number): Longitude.
- `port` (string): Station slug.

### `get_astronomy` (~99 tokens)

Get sun and moon data: sunrise, sunset, dawn, dusk, day length, moon phase, illumination, moonrise, moonset.

Input parameters:

- `date` (string): Start date YYYY-MM-DD (default: today).
- `days` (integer): Number of days, 1-7 (default: 1).
- `lat` (number): Latitude.
- `lon` (number): Longitude.
- `port` (string): Station slug.

### `get_conditions` (~94 tokens)

Get unified weather + marine + astronomy data in one call. More efficient than calling each separately.

Input parameters:

- `days` (integer): Forecast days, 1-7 (default: 3).
- `include` (string): Comma-separated list: weather,marine,astronomy (default: all three).
- `lat` (number): Latitude.
- `lon` (number): Longitude.
- `port` (string): Station slug.

### `get_history` (~101 tokens)

Get historical tide predictions and weather data for past dates. Tides up to 365 days, weather up to 90 days.

Input parameters:

- `date` (string, required): Start date in the past, YYYY-MM-DD (required).
- `days` (integer): Number of days, 1-365 (default: 7).
- `include` (string): Comma-separated: tides,weather (default: tides).
- `port` (string, required): Station slug (required).

### `get_observations` (~91 tokens)

Get real-time sea level observations from REFMAR/SHOM tide gauges (French stations only). Returns 10-minute interval readings.

Input parameters:

- `date` (string): Start date YYYY-MM-DD (default: today).
- `days` (integer): Number of days, 1-7 (default: 1).
- `port` (string, required): Station slug (must be a French REFMAR station).

### `get_radar` (~56 tokens)

Get rain radar tile URLs for a location. Returns past frames and short-term nowcast frames for map overlays.

Input parameters:

- `lat` (number): Latitude.
- `lon` (number): Longitude.
- `port` (string): Station slug.

## Diagnostics

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

## Score history

- 2026-11-05: 70
- 2026-11-04: 69
- 2026-11-03: 62

## Common questions

### What is the TidesAtlas MCP server?

TidesAtlas is an MCP server listed in the public MCP registry as com.tidesatlas/tides. Worldwide tide times and heights, marine weather, sea temperature, sun and moon for 13,000+ ports. This page covers its hosted endpoint (https://tidesatlas.com/mcp).

### Is the TidesAtlas MCP server safe to use?

TidesAtlas scores 70 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 TidesAtlas MCP server expose?

TidesAtlas exposes 10 tools: get_tides, search_ports, list_countries, get_weather, get_marine, and 5 more. Their descriptions and schemas cost roughly 917 tokens of context every time the server is loaded.

### Does the TidesAtlas MCP server require authentication?

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

### Is the TidesAtlas MCP server still maintained?

TidesAtlas is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tidesatlas.com/mcp
- Authorisation metadata: https://tidesatlas.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/TidesAtlas/tidesatlas-api
- Website: https://tidesatlas.com/en/api/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-tidesatlas-tides/tidesatlas.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tidesatlas-tides/tidesatlas.json
- HTML version of this page: https://verifymcp.io/servers/com-tidesatlas-tides/tidesatlas