Skip to content
TidesAtlas logo

TidesAtlas MCP server

Which MCP servers are TidesAtlas's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-03

← Back to TidesAtlas

Whose server it is
  • Registry namecom.tidesatlas/tidesverified in the MCP registry

The registry name sits under tidesatlas.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-03
  • Stateanswerschecked 2026-11-03
  • Tools10
  • Server calls itselfTidesAtlas
  • Server version1.1.0
  • Protocol version2024-11-05

On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 449 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check tide times and heights for a chosen port; review wave, wind and weather forecasts before going out on the water; pull tide and weather data into an app through a REST API.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "check tide times and heights for a chosen port", the likely first call is get_tides.
  • For "review wave, wind and weather forecasts before going out on the water", the likely first call is get_conditions.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-11-03
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer598 ms
  • Space in an agent's context≈ 1,279 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · check tide times and heights for a chosen port
  • can do · review wave, wind and weather forecasts before going out on the water
  • can do · pull tide and weather data into an app through a REST API

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-11-03
  • get_tides

    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 18,400+ stations worldwide.

  • search_ports

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

  • list_countries

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

  • get_weather

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

  • get_marine

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

  • get_astronomy

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

  • get_conditions

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

  • get_history

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

  • get_observations

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

  • get_radar

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "tides": {
      "type": "http",
      "url": "https://tidesatlas.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http tidesatlas https://tidesatlas.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://tidesatlas.com/mcp as a custom connector in the settings.

OpenAPI spec

13 paths, read 2026-11-03. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.