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.

Shiptrail

REMOTE · SHIPTRAIL.IO

Free live AIS ship tracking: find any ship by name, MMSI or IMO, and see who is arriving at a port.

Available components

73 Trust /100

Last scanned (14 hours ago)

Scores higher than 60% 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 Security80
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 608 tokens (~152/item across 4 items; 4 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 Management3
  • Stability observed for 1 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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 0
    • Tool “get_ship” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • “get_ship” added an optional parameter “includeNearby” cosmetic
  • 4 Nov 26 73

    First indexed and scored.

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://shiptrail.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=shiptrail.io CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 7fdac5f35b5faf531360508cce156da3
SANs: shiptrail.io, notify.shiptrail.io, *.notify.shiptrail.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of shiptrail.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
shiptrail.io. 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
Header Value
strict-transport-security max-age=15552000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'sha256-DtU0GOsixN25OjpmoW1qjJNVupzeEHy5SQwxi4G7dYg=' https://cdnjs.cloudflare.com/ajax/libs/maplibre-gl/4.7.1/; style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com/ajax/libs/maplibre-gl/4.7.1/; img-src 'self' data: blob: https: https://thumb.wikimedia.org; connect-src 'self' https://basemaps.cartocdn.com https://*.basemaps.cartocdn.com https://tiles.openfreemap.org https://tile.openstreetmap.org https://tiles.openseamap.org https://gis.charttools.noaa.gov https://api.rainviewer.com https://tilecache.rainviewer.com https://api.open-meteo.com https://marine-api.open-meteo.com https://commons.wikimedia.org; worker-src blob:; child-src blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://shiptrail.io/mcp Verified 200
http (plaintext) http://shiptrail.io/mcp HTTPS enforced 301 https://shiptrail.io/mcp
MCP tools · 4 exposed · ~420 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
get_port ~110

A port's Arrivals board (ships in port now, then ships en route by ETA) and Departures board (ships that left in the last 48 hours), as its Shiptrail page shows them, by UN/LOCODE. Each row carries the ship's MMSI for get_ship.

NameTypeReqDescription
limitinteger–At most this many rows on each list; the counts are always whole.
locodestringyesThe port's UN/LOCODE, such as USHNL.
NameTypeReqDescription
arrivalsobjectyes–
countsobjectyes–
departuresarrayyes–
portobjectyes–
truncatedboolean–True when a list was cut to the limit.
urlstringyesHer page, or the port's, on shiptrail.io.

No examples provided.

get_ship ~122

Everything Shiptrail's page shows about one ship, by MMSI: identity, size, position, speed, course and status, destination and ETA, where she came from, recent port calls, particulars and registry facts, photo and its credit, a Wikipedia summary, and, with includeNearby, the ships near her. No history over time.

NameTypeReqDescription
includeNearbyboolean–Also list the ships near her. Off by default; leave it off unless the question is about her surroundings.
mmsiintegeryesHer MMSI, 9 digits.
NameTypeReqDescription
aisClassstring––
beamMnumber––
callSignstring––
dossierstring–pending: her particulars and photo are still being looked up; ask again in a minute.
draughtMnumber––
flagstring––
imointeger––
kindstring–The map's class for her AIS type.
lastHeardstring–Her last position report.
lengthMnumber––
mmsiintegeryes–
namestringyes–
nearbyarray––
onMapbooleanyes–
particularsobject–From Wikidata and the US Coast Guard, where they know her.
photoobject––
positionobject–Where she is, as she last broadcast it. For a ship off the map, where she was last heard.
recentCallsarray––
sharesImoWitharray–Other MMSIs heard with her IMO number.
typestring––
urlstringyesHer page, or the port's, on shiptrail.io.
voyageobject––
wikipediaobject––

No examples provided.

search_ports ~84

Find ports by name or UN/LOCODE. Busy ports come first, with how many ships are in port, en route and lately departed. Use get_port with a UN/LOCODE for its boards.

NameTypeReqDescription
limitinteger–At most this many ports.
querystringyesA port's name or part of it, or its UN/LOCODE.
NameTypeReqDescription
portsarrayyes–
querystringyes–

No examples provided.

search_ships ~104

Find ships by name, MMSI (9 digits) or IMO number (7 digits): every ship with a Shiptrail page, any class, on the map now or heard in the last year. Ships on the map now come first. Use get_ship with an MMSI for the whole record.

NameTypeReqDescription
limitinteger–At most this many ships.
querystringyesA ship's name or part of it, an MMSI or an IMO number.
NameTypeReqDescription
notestring–Why the list may be short.
querystringyes–
shipsarrayyes–

No examples provided.

Install

How do I install the Shiptrail MCP server?

Shiptrail is a hosted endpoint at https://shiptrail.io/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 · shiptrail.io

# add to Claude Code
claude mcp add --transport http io-shiptrail-shiptrail 'https://shiptrail.io/mcp'
Common questions

What is the Shiptrail MCP server?

Shiptrail is an MCP server listed in the public MCP registry as io.shiptrail/shiptrail. Free live AIS ship tracking: find any ship by name, MMSI or IMO, and see who is arriving at a port. This page covers its hosted endpoint (https://shiptrail.io/mcp).

Is the Shiptrail MCP server safe to use?

Shiptrail scores 73 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 Shiptrail MCP server expose?

Shiptrail exposes 4 tools: search_ships, get_ship, search_ports, get_port. Their descriptions and schemas cost roughly 420 tokens of context every time the server is loaded.

Does the Shiptrail MCP server require authentication?

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

Is the Shiptrail MCP server still maintained?

Shiptrail 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.