Data Collection

aistrail.com

Provides AIS-based tools for searching, locating, and tracking vessels, including detailed ship information, area and proximity queries, and historical tracks.

1 endpoint9 known toolsFirst detected October 17, 2026Last detected October 17, 2026

ENDPOINT 1

https://api.aistrail.com/mcp

No auth detected

MCP server metadata

Name: aistrail-ais
Version: 1.4.0

Capabilities

tools

Server instructions

AIS Trail: ship positions from AIS. Live tools (no key) cover ships heard in the last hour worldwide via community and government feeds, plus last known positions up to 7 days for ships out of receiver range. vessel_track returns history (since October 2026 for worldwide coastal coverage from community receivers and for Finnish and Norwegian waters, up to 12 months for Danish waters, calendar year 2025 for U.S. waters) and needs an AIS Trail API key sent as the HTTP header 'Authorization: Bearer ap_live_…', so it works only in MCP clients that let you add a header. vessel_port_calls and port_calls return port calls (arrival, departure, draught, previous and next port) from the same archive and need the same key; these three use the plan's credits as the REST API does. find_port finds port ids without a key. Positions are what ships broadcast; times are UTC. Always credit the sources listed in each result's attribution. Private vessels (pleasure craft, sailing vessels and Class B transponders without a valid IMO number) are never listed or looked up individually; area and nearby results report how many were left out (private_vessels). Not for navigation. AIS data can be missing, delayed or wrong; do not use it for navigation, collision avoidance, search and rescue or any other safety-of-life purpose.

Known tools 9

search_vessels

Find ships by name (or part of it), MMSI (9 digits) or IMO number (7 digits).

Inferred read-only

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, its track over the last 40 minutes, and the data sources to credit.

Inferred read-only

vessels_in_area

Ships heard in the last hour inside a box (at most 5° on each side), largest first.

Inferred read-only

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.

Inferred read-only

vessel_track

Where a ship has been between two times (UTC, ISO 8601), from the AIS Trail archive.

Inferred read-only

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 vessel_track can return for that source on plans without live data), and the service status: ok or degraded, with reason codes in reasons.

Inferred read-only

find_port

Find ports by name (or part of it), UN/LOCODE (e.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.aistrail-ais]
url = "https://api.aistrail.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: aistrail-ais
Remote MCP URL: https://api.aistrail.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "aistrail-ais": {
      "url": "https://api.aistrail.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "aistrail-ais",
  "transport": "streamable-http",
  "url": "https://api.aistrail.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.