Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AIS Trail

REMOTE · API.AISTRAIL.COM

Live AIS ship positions, vessel history, port calls and events, plus sanctions flags. Read-only.

Available components

+10 this week 78 Trust /100

Last scanned (2 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3218 tokens (~292/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1
    • Tool “vessel_port_calls” rewrote its description, which is the text the model reads security
  • 2 Nov 26 +5
    • HTTPS: unverified → pass ▲ security
  • 1 Nov 26 +2
    • Tool coverage: 49% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • “find_port” reworded the description of “limit” cosmetic
    • “port_calls” reworded the description of “event” cosmetic
    • “port_calls” reworded the description of “port_id” cosmetic
    • “search_vessels” reworded the description of “limit” cosmetic
    • “vessel_events” reworded the description of “imo” cosmetic
    • “vessel_events” reworded the description of “mmsi” cosmetic
    • “vessel_port_calls” reworded the description of “imo” cosmetic
    • “vessel_port_calls” reworded the description of “mmsi” cosmetic
    • “vessel_track” reworded the description of “mmsi” cosmetic
    • “vessel_track” reworded the description of “resolution” cosmetic
    • “vessels_in_area” reworded the description of “limit” cosmetic
    • “vessels_in_area” reworded the description of “max_lat” cosmetic
    • “vessels_in_area” reworded the description of “max_lon” cosmetic
    • “vessels_in_area” reworded the description of “min_lat” cosmetic
    • “vessels_in_area” reworded the description of “min_lon” cosmetic
    • “vessels_near” reworded the description of “lat” cosmetic
    • “vessels_near” reworded the description of “limit” cosmetic
    • “vessels_near” reworded the description of “lon” cosmetic
    • “vessels_near” reworded the description of “radius_nm” cosmetic
  • 30 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_port” rewrote its description, which is the text the model reads security
  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1
    • Server version: 1.5.1 → 1.5.2 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://api.aistrail.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aistrail.com CN=YE2,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 6bffb9e0e27c3577b4b710a37d62191eb8a
SANs: *.aistrail.com, aistrail.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.aistrail.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
aistrail.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.aistrail.com/mcp Verified 200
http (plaintext) http://api.aistrail.com/mcp HTTPS enforced 301 https://api.aistrail.com/mcp
MCP tools · 11 exposed · ~2,831 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
data_status ~86

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_port ~162

Find ports by name (or part of it), UN/LOCODE (e.g. FIHEL) or two-letter country code (e.g. FI) in the port reference (World Port Index and UN/LOCODE ports): id (for port_calls), name, country, UN/LOCODE, position, harbor size (World Port Index ports only) and the radius of the port area used to detect port calls. At most 20 ports, larger harbors first. No API key needed.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country code
limitinteger–Maximum number of ports to return
locodestring–UN/LOCODE
querystring–Port name

No output schema declared.

No examples provided.

get_vessel ~193

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. flag (ISO code) and flag_country come from the MMSI: the flag of the radio licence, usually but not always the registry flag. dwt_estimate is an estimate from the AIS dimensions (tonnes, size class such as Panamax or VLCC, hull, draught used), not a registry value; null for tugs, pleasure craft and other types where deadweight does not apply. For archive records and sanctions flags, use lookup_vessels (API key).

NameTypeReqDescription
mmsiintegeryes9-digit MMSI

No output schema declared.

No examples provided.

lookup_vessels ~255

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 flags by IMO number from three official lists: OFAC SDN, UK Sanctions List and EU Regulation 833/2014 Annex XLII (list, programmes, date listed). An IMO number resolves to the MMSI that reported it last; ships not in the plan's sources come back with found false. Sanctions flags are informational, not a compliance determination: only ships a list names by IMO number are matched, ownership-based sanctions are not covered. Needs an AIS Trail API key sent by the MCP client as the HTTP header 'Authorization: Bearer ap_live_…'. Credits: 1 per ship returned (none for ships not found); the plan's sources and 24-hour delay (on plans without live data) apply.

NameTypeReqDescription
imoarray–7-digit IMO numbers; mmsi and imo together at most 20
mmsiarray–9-digit MMSIs

No output schema declared.

No examples provided.

port_calls ~277

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 from find_port. event: any (in port at any time in the range, default), arrival or departure. The sanctions column gives the codes of the sanctions lists (OFAC, UK, EU) that name the ship's IMO number; informational only, not a compliance determination. Needs an AIS Trail API key sent by the MCP client as the HTTP header 'Authorization: Bearer ap_live_…'. At most 100 port calls per call and at most 366 days; the plan's rules and credits (1 per port call returned) apply as for vessel_port_calls.

NameTypeReqDescription
eventstring–any: in port at any time in the range; arrival: arrived in the range; departure: departed in the range
fromstringyesStart, e.g. 2026-09-01T00:00:00Z
port_idintegeryesPort id from find_port
tostringyesEnd, e.g. 2026-09-02T00:00:00Z

No output schema declared.

No examples provided.

search_vessels ~190

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 code from the MMSI), lat, lon, speed_kn, course_deg, length_m, destination, age_s, status, source); call get_vessel for full details of one ship. 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).

NameTypeReqDescription
limitinteger–Maximum number of ships to return
querystringyesShip name, MMSI (9 digits) or IMO (7 digits)

No output schema declared.

No examples provided.

vessel_events ~573

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 oldest day the plan includes), as on the REST endpoint. Give mmsi or imo (with imo, every MMSI that reported that IMO number in the range). Types: ENTER_ZONE and EXIT_ZONE (arrival at and departure from a port or anchorage; port_id for port_calls, zone port or anchorage), STATE_CHANGED (MOVING, NOT_MOVING, LONG_STOP), NAME_CHANGED, IMO_CHANGED, CALLSIGN_CHANGED, DESTINATION_CHANGED and DRAUGHT_CHANGED (old and new value); only when asked by name or with types ['all']: AIS_GAP (long AIS silence while under way; old_value hours, new_value nautical miles), ENCOUNTER (slow close approach to another ship outside port areas, a candidate ship-to-ship transfer; new_value the other ship's MMSI), FLAG_CHANGED (the IMO number reappears under an MMSI with another flag) and POSITION_JUMP (a physically impossible position jump). Rows: [time, event, old_value, new_value, lat, lon, mmsi, port_id, zone, sanctions, detail]; detail says more about behaviour events. The sanctions column gives the codes of the sanctions lists (OFAC, UK, EU) that name the ship's IMO number; informational only, not a compliance determination. Needs an AIS Trail API key sent by the MCP client as the HTTP header 'Authorization: Bearer ap_live_…'. At most 200 events per call and at most 31 days; the plan's history depth, credits (1 per event returned), rate limit and 24-hour delay (on plans without live data) apply.

NameTypeReqDescription
fromstring–Start, e.g. 2026-10-01T00:00:00Z; default: 7 days before to (on Free, no earlier than the oldest day the plan includes)
imointeger–7-digit IMO number; covers every MMSI that reported it in the range. Give mmsi or imo
mmsiinteger–9-digit MMSI of the ship; give mmsi or imo
tostring–End, e.g. 2026-10-08T00:00:00Z; default: now (24 hours ago on plans without live data)
typesarray–Event types; default: every type except AIS_GAP, ENCOUNTER, FLAG_CHANGED, POSITION_JUMP. ['all'] for every type.

No output schema declared.

No examples provided.

vessel_port_calls ~301

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. Give mmsi or imo. A port call starts when the ship stops inside a port area and ends when it leaves; departure is null while it is still in port. The sanctions column gives the codes of the sanctions lists (OFAC, UK, EU) that name the ship's IMO number; informational only, not a compliance determination. Needs an AIS Trail API key sent by the MCP client as the HTTP header 'Authorization: Bearer ap_live_…'. At most 100 port calls per call and at most 366 days; the plan's history depth, credits (1 per port call returned), rate limit and 24-hour delay (on plans without live data) apply.

NameTypeReqDescription
fromstringyesStart, e.g. 2026-09-01T00:00:00Z
imointeger–7-digit IMO number of the ship; give mmsi or imo
mmsiinteger–9-digit MMSI of the ship; give mmsi or imo
tostringyesEnd, e.g. 2026-10-01T00:00:00Z

No output schema declared.

No examples provided.

vessel_track ~342

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 cannot add headers (OAuth-only web connectors) cannot use it yet. Resolution: raw (up to 24 h per call), 1m (up to 7 days) or 1h (up to 366 days); at most 200 points per call, as rows of [time, lat, lon, speed_kn, course_deg]. The plan's history depth, credits (as on the track endpoint: 1 per vessel-day) and rate limit apply, and the 24-hour delay on recent data on plans without live data. sources_through gives, per source, the time up to which the archive holds its data; pending_days lists days in the range a source has not delivered yet, so no points on those days does not mean the ship was absent.

NameTypeReqDescription
fromstringyesStart, e.g. 2026-10-01T00:00:00Z
mmsiintegeryes9-digit MMSI of the ship
resolutionstring–raw: every position (up to 24 h per call); 1m: one point per minute (up to 7 days); 1h: one point per hour (up to 366 days)
tostringyesEnd, e.g. 2026-10-02T00:00:00Z

No output schema declared.

No examples provided.

vessels_in_area ~220

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, source); call get_vessel for full details of one ship. 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).

NameTypeReqDescription
limitinteger–Maximum number of ships to return
max_latnumberyesNorthern edge of the box, decimal degrees
max_lonnumberyesEastern edge of the box, decimal degrees
min_latnumberyesSouthern edge of the box, decimal degrees
min_lonnumberyesWestern edge of the box, decimal degrees
ship_typestring–Optional type filter

No output schema declared.

No examples provided.

vessels_near ~232

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, length_m, destination, age_s, status, source); call get_vessel for full details of one ship. 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).

NameTypeReqDescription
latnumber–Latitude of the centre, decimal degrees (with lon, or give mmsi)
limitinteger–Maximum number of ships to return
lonnumber–Longitude of the centre, decimal degrees (with lat, or give mmsi)
mmsiinteger–Use this ship's position as the centre instead of lat/lon
radius_nmnumber–Search radius in nautical miles

No output schema declared.

No examples provided.

Install

How do I install the AIS Trail MCP server?

AIS Trail is a hosted endpoint at https://api.aistrail.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.

remote · api.aistrail.com

# add to Claude Code
claude mcp add --transport http com-aistrail-ais 'https://api.aistrail.com/mcp'
Common questions

What is the AIS Trail MCP server?

AIS Trail is an MCP server listed in the public MCP registry as com.aistrail/ais. Live AIS ship positions, vessel history, port calls and events, plus sanctions flags. Read-only. This page covers its hosted endpoint (https://api.aistrail.com/mcp).

Is the AIS Trail MCP server safe to use?

AIS Trail scores 78 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 AIS Trail MCP server expose?

AIS Trail exposes 11 tools: search_vessels, get_vessel, vessels_in_area, vessels_near, vessel_track, and 6 more. Their descriptions and schemas cost roughly 2,831 tokens of context every time the server is loaded.

Does the AIS Trail MCP server require authentication?

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

Is the AIS Trail MCP server still maintained?

AIS Trail 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.