Skip to content
AIS Trail logo

AIS Trail MCP server

Which MCP servers are AIS Trail'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-10-27

← Back to AIS Trail

Whose server it is
  • Registry namecom.aistrail/aisverified in the MCP registry

The registry name sits under aistrail.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-10-27
  • Stateanswerschecked 2026-10-27
  • Tools11
  • Server calls itselfaistrail-ais
  • Server version1.5.2
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 550 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: trace where a ship sailed over a chosen period; check a vessel's past voyages before insuring or chartering it.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "trace where a ship sailed over a chosen period", the likely first call is vessel_track.
  • For "check a vessel's past voyages before insuring or chartering it", the likely first call is search_vessels.
  • Parameters are untyped or undescribed in 8 of 11 tools: check arguments before calling.

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-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer537 ms
  • Space in an agent's context≈ 3,265 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsB · 88 of 100
  • Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 8 of 11

What an agent can do with it

  • can do · trace where a ship sailed over a chosen period
  • not sure · calculate how long ships waited at anchor
  • can do · check a vessel's past voyages before insuring or chartering it

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 offers11 tools · read 2026-10-27
  • search_vessels

    Find ships by name (or part of it), MMSI (9 digits) or IMO number (7 digits). Returns live ships first, then ships out of range with their last known position (up to 7 days). List results are compact rows (mmsi, name, category, flag (ISO…

  • get_vessel

    Everything known about one ship now: identity (name, IMO, call sign, flag, type, size), last position, speed, course, heading, navigational status, destination (port codes decoded) and ETA as given by the crew, how long ago it was heard…

  • vessels_in_area

    Ships heard in the last hour inside a box (at most 5° on each side), largest first. List results are compact rows (mmsi, name, category, flag (ISO code from the MMSI), lat, lon, speed_kn, course_deg, length_m, destination, age_s, status…

  • vessels_near

    Ships heard in the last hour within a radius (at most 50 nautical miles) of a point or of another ship, nearest first. List results are compact rows (mmsi, name, category, flag (ISO code from the MMSI), lat, lon, speed_kn, course_deg…

  • vessel_track

    Where a ship has been between two times (UTC, ISO 8601), from the AIS Trail archive. Needs an AIS Trail API key sent by the MCP client as the HTTP header 'Authorization: Bearer ap_live_…' (keys at https://aistrail.com); clients that…

  • data_status

    How many ships are live now (live_ships_private: how many of them are private vessels, counted only), how many are known from the last 7 days, the date range of the history archive per source with available_until (the latest time…

  • find_port

    Find ports by name (or part of it), UN/LOCODE (e.g. NLRTM) or two-letter country code (e.g. NL) in the port reference (World Port Index and UN/LOCODE ports): id (for port_calls), name, country, UN/LOCODE, position, harbor size (World Port…

  • vessel_port_calls

    Port calls of a ship between two times (UTC, ISO 8601), from the AIS Trail archive: port, arrival, departure, draught on arrival and departure, cargo estimate (loaded, ballast or unchanged, from the draught change), previous and next…

  • port_calls

    Ships that called at one port between two times (UTC, ISO 8601), from the AIS Trail archive: ship (with its flag from the MMSI), arrival, departure, draught on arrival and departure, cargo estimate, previous and next port. Get the port_id…

  • vessel_events

    Events of a ship between two times (UTC, ISO 8601), computed from the AIS Trail archive. from and to are optional: without to, now (24 hours ago on plans without live data); without from, 7 days before to (on Free, no earlier than the…

  • lookup_vessels

    Records of up to 20 ships at once from the AIS Trail archive, by mmsi and/or imo (lists): identity and particulars (name, IMO, call sign, type, flag from the MMSI, length, beam, estimated deadweight, first and last seen) and sanctions…

How to connect

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

{
  "mcpServers": {
    "ais": {
      "type": "http",
      "url": "https://api.aistrail.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http aistrail https://api.aistrail.com/mcp

Add to CursorAdd to VS Code

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

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.