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.

Gangway AIS

REMOTE · GANGWAYAIS.COM

Vessels, ports, port calls and waiting times at anchor from licensed AIS. Read only; needs a key.

Available components

+3 this week 75 Trust /100

Last scanned (13 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3524 tokens (~167/item across 21 items; 21 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 Management23
  • Stability observed for 7 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1
    • Tool “check_route” rewrote its description, which is the text the model reads security
    • Tool “depth_at” rewrote its description, which is the text the model reads security
    • Tool “plan_route” rewrote its description, which is the text the model reads security
    • Tool “port_calls_on_date” rewrote its description, which is the text the model reads security
    • Tool “port_congestion” rewrote its description, which is the text the model reads security
    • Tool “port_events” rewrote its description, which is the text the model reads security
    • Tool “port_vessels” rewrote its description, which is the text the model reads security
    • Tool “port_waiting_times” rewrote its description, which is the text the model reads security
    • Tool “sanctions_check” rewrote its description, which is the text the model reads security
    • Tool “vessel_activity” rewrote its description, which is the text the model reads security
    • Tool “vessel_port_calls” rewrote its description, which is the text the model reads security
    • Tool “vessel_track” rewrote its description, which is the text the model reads security
    • Tool “vessels_in_area” rewrote its description, which is the text the model reads security
    • Tool “vessels_near” rewrote its description, which is the text the model reads security
  • 20 Nov 26 0
    • “port_events” reworded the description of “kinds” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 19 Nov 26 +1

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

  • 18 Nov 26 0
    • Tool “check_route” rewrote its description, which is the text the model reads security
    • Tool “depth_at” rewrote its description, which is the text the model reads security
    • Tool “plan_route” rewrote its description, which is the text the model reads security
    • Tool “port_calls_on_date” rewrote its description, which is the text the model reads security
    • Tool “port_congestion” rewrote its description, which is the text the model reads security
    • Tool “port_events” rewrote its description, which is the text the model reads security
    • Tool “port_vessels” rewrote its description, which is the text the model reads security
    • Tool “port_waiting_times” rewrote its description, which is the text the model reads security
    • Tool “sanctions_check” rewrote its description, which is the text the model reads security
    • Tool “vessel_activity” rewrote its description, which is the text the model reads security
    • Tool “vessel_port_calls” rewrote its description, which is the text the model reads security
    • Tool “vessel_track” rewrote its description, which is the text the model reads security
  • 16 Nov 26 +1

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

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 72

    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 21 Nov 2026 · Probed https://gangwayais.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gangwayais.com CN=YE1,O=Let's Encrypt,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA384 6a4223639662a870c7ac4af36615c11d790
SANs: gangwayais.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 gangwayais.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
gangwayais.com. No DS 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=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
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://gangwayais.com/mcp Verified 200
http (plaintext) http://gangwayais.com/mcp HTTPS enforced 308 https://gangwayais.com/mcp
MCP tools · 21 exposed · ~3,293 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
account_usage ~77

Your key's plan, the credits used and left this month, when they renew, and the plan's rate, largest box, reach back and delay. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_route ~219

Check a planned route leg by leg against land, depth (her draught plus the under-keel clearance), sea room and the traffic separation schemes, with plain-language warnings for what it finds. A planning aid: it finds what our charts and data show, never everything; not for navigation. At most 30 a minute. Credits: 10. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
air_draught_mnumber–Her air draught in metres
beam_mnumber–Her beam in metres
draught_mnumber–Her draught in metres
length_mnumber–Her length overall in metres
sea_room_nmnumber–Sea room to keep off danger, in nautical miles
ukc_mnumber–Under-keel clearance to keep, in metres
waypointsarrayyesThe route's turning points in order, each [lat, lon]

No output schema declared.

No examples provided.

data_sources ~75

The sources behind the answers, each with its licence, the credit to show and what it covers, and how far back our recorded history goes. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

depth_at ~105

The charted water depth at a position from EMODnet Bathymetry (European waters), or none where it has no figure. Not for navigation. Credits: 1, nothing where there is no depth. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
latnumberyesLatitude in decimal degrees, north positive
lonnumberyesLongitude in decimal degrees, east positive

No output schema declared.

No examples provided.

get_vessel ~157

One vessel now: her last position, speed, course, heading and navigational status from a source we may pass on, with her particulars (name, IMO, call sign, type, size, flag) and voyage (destination, ETA, draught). Give her MMSI, or her IMO number (then she is found by search first, 1 credit more). Credits: 1. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

NameTypeReqDescription
imointeger–The vessel's IMO number, seven digits
mmsiinteger–The vessel's MMSI, nine digits

No output schema declared.

No examples provided.

plan_route ~184

A sea route between two positions, through the traffic separation schemes, with its distance and legs. Give the vessel's length and draught to keep her in water deep enough. A planning aid from charts and data that can be wrong: never for navigation. At most 6 a minute. Credits: 10. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
draught_mnumber–Her draught in metres
from_latnumberyesLatitude in decimal degrees, north positive
from_lonnumberyesLongitude in decimal degrees, east positive
length_mnumber–Her length overall in metres
to_latnumberyesLatitude in decimal degrees, north positive
to_lonnumberyesLongitude in decimal degrees, east positive

No output schema declared.

No examples provided.

port_calls_on_date ~122

The seagoing vessels alongside in a port on one UTC day (default today), with when each made fast and left. Reach back: as set in your Data API agreement. Credits: 1 per call. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
datestring–The day, YYYY-MM-DD (UTC)
portstringyesA port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

No output schema declared.

No examples provided.

port_congestion ~129

How busy a port is against its own normal: an index, vessels waiting now, the median wait and the arrivals and departures day by day over the last days (default 30). Credits: 5, nothing when we hold no figures for it. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
daysinteger–Days back from now (default 30)
portstringyesA port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

No output schema declared.

No examples provided.

port_events ~259

Recent events from AIS: arrivals, departures, anchoring, weighing anchor and approaches by default; also pilot, tug, bunkering, waiting, renamed and more. Optionally inside a box (at most 400 square degrees). Since defaults to the last 24 hours, at most 30 days back. Credits: 1 per event. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
kindsstring–Comma-separated kinds, or "all". Kinds: aground, aisoff, anchored, approaching, arrived, bunkering, delayrisk, destination, dragging, draught, drifting, eta, heard, left, pilot, quiet, renamed, slow,…
limitinteger–At most this many events (default 60)
max_latnumber–North edge of the box
max_lonnumber–East edge of the box
min_latnumber–South edge of the box
min_lonnumber–West edge of the box
sincestring–ISO 8601 UTC time to start from

No output schema declared.

No examples provided.

port_now ~138

A port's picture now: vessels in port and at anchor, vessels expected (arriving) and the latest port events. Give a UN/LOCODE or a name. Credits: 5, nothing when the port is empty. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

NameTypeReqDescription
limitinteger–At most this many vessels in each list (default 40)
portstringyesA port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

No output schema declared.

No examples provided.

port_vessels ~200

A port's list of vessels: expected (bound for it), in port now, arrived or departed over the last 7 days. Filter by kind, flag and length. Credits: 1 per vessel returned. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
flagstring–Only this flag, a two-letter ISO country code
kindstring–Only this kind of vessel
limitinteger–At most this many vessels (default 50)
liststring–Which list (default expected)
max_length_mnumber–Only vessels at most this long, in metres
min_length_mnumber–Only vessels at least this long, in metres
portstringyesA port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

No output schema declared.

No examples provided.

port_waiting_times ~123

Waiting times at anchor off a port: the median this week against what is normal there, and optionally the vessels waiting now. Credits: 5, nothing when we hold no figures for it. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
include_vesselsboolean–Also list the vessels at anchor now (default false)
portstringyesA port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

No output schema declared.

No examples provided.

resolve_destination ~86

The port an AIS destination text names (such as "NL RTM" or "ROTTERDAM PILOT"), or null. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

NameTypeReqDescription
destinationstringyesThe destination as the vessel broadcasts it

No output schema declared.

No examples provided.

sanctions_check ~119

Whether a vessel's IMO number is on the public sanctions lists we read (the US OFAC SDN list, the UK Sanctions List, the EU vessel lists and Australia's sanctioned vessels), with what each list says of her. Matched by IMO number only: information, not a compliance determination. Credits: 1. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
imointegeryesThe vessel's IMO number, seven digits with a valid check digit

No output schema declared.

No examples provided.

search_ports ~133

Ports by name, UN/LOCODE or English name, ranked for a seafarer; or the ports nearest a position. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

NameTypeReqDescription
limitinteger–At most this many ports (default 8)
near_latnumber–Or: the ports nearest this latitude
near_lonnumber–Or: the ports nearest this longitude
querystring–A port name or UN/LOCODE

No output schema declared.

No examples provided.

search_vessels ~182

Find vessels by name, MMSI or IMO number (a prefix of at least 2 characters works), among the vessels our sources have heard. Each comes with her particulars and her last position from a source we may pass on. Use it to turn a name into an MMSI for the other tools. Credits: 1 per vessel returned. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

NameTypeReqDescription
limitinteger–At most this many vessels (default 10)
near_latnumber–Optional: rank vessels near this latitude first
near_lonnumber–Optional: rank vessels near this longitude first
querystringyesName, MMSI or IMO, or the start of one

No output schema declared.

No examples provided.

vessel_activity ~132

A summary of how a vessel spent the last days (default 30): hours under way, in port, stopped off a port, stopped elsewhere and not heard, the distance sailed, her speeds, her calls and the ports she called at most. Reach back: as set in your Data API agreement. Credits: 5. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
daysinteger–Days back from now (default 30)
mmsiintegeryesThe vessel's MMSI, nine digits

No output schema declared.

No examples provided.

vessel_port_calls ~141

Where a vessel called, from when to when, the gaps when no receiver heard her and the events along the way, for the last days asked (default 7), from all the AIS we hear (the ports and times; a position only where we may pass it on). Reach back: as set in your Data API agreement. Credits: 1 per call. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
daysinteger–Days back from now (default 7)
mmsiintegeryesThe vessel's MMSI, nine digits

No output schema declared.

No examples provided.

vessel_track ~201

One vessel's recorded positions, oldest first, from the sources we may pass on: give hours back from now (default 72) or a from/to window. Long tracks are thinned evenly to max_points for reading; the credits count the whole range. Reach back: as set in your Data API agreement. Credits: 1 per vessel-day with positions. Needs a paid plan: a paid Watch plan, or the Data API by agreement (write to desk@gangwayais.com).

NameTypeReqDescription
fromstring–Start, ISO 8601 UTC such as 2026-11-01T00:00:00Z
hoursinteger–Hours back from now
max_pointsinteger–Hand back at most this many points (default 300)
mmsiintegeryesThe vessel's MMSI, nine digits
tostring–End, ISO 8601 UTC (default now)

No output schema declared.

No examples provided.

vessels_in_area ~263

Vessels inside a latitude/longitude box, newest report first, each at her last position from a source we may pass on. truncated says that more were left out. Largest box: 1 square degree on a free account, otherwise as set in your Data API agreement. Credits: 1 per vessel returned. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

NameTypeReqDescription
limitinteger–At most this many vessels (default 50)
max_agestring–Only vessels heard within this time, such as 90m, 24h or 7d (default 24h)
max_latnumberyesNorth edge of the box
max_lonnumberyesEast edge of the box
min_latnumberyesSouth edge of the box
min_lonnumberyesWest edge of the box
min_speed_knnumber–Only vessels at or above this speed over ground, in knots
ship_typeinteger–AIS ship type: a code ending in 0 means its whole group (70 all cargo, 80 all tankers)

No output schema declared.

No examples provided.

vessels_near ~248

Vessels within a radius of a position or of another vessel, nearest first, each with her distance in nautical miles and true bearing from the centre. It asks for the square around the circle, which must fit your plan's largest box (1 square degree on a free account, otherwise as set in your Data API agreement). Credits: 1 for every vessel in that square (at most 200), and 1 more to centre on a vessel. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

NameTypeReqDescription
latnumber–Latitude in decimal degrees, north positive
limitinteger–At most this many vessels (default 25)
lonnumber–Longitude in decimal degrees, east positive
max_agestring–Only vessels heard within this time, such as 90m or 24h (default 24h)
mmsiinteger–Or centre on this vessel's last position
radius_nmnumber–Radius in nautical miles (default 10, at most 30)

No output schema declared.

No examples provided.

Install

How do I install the Gangway AIS MCP server?

Gangway AIS is a hosted endpoint at https://gangwayais.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 · gangwayais.com

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

What is the Gangway AIS MCP server?

Gangway AIS is an MCP server listed in the public MCP registry as com.gangwayais/ais. Vessels, ports, port calls and waiting times at anchor from licensed AIS. Read only; needs a key. This page covers its hosted endpoint (https://gangwayais.com/mcp).

Is the Gangway AIS MCP server safe to use?

Gangway AIS scores 75 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 Gangway AIS MCP server expose?

Gangway AIS exposes 21 tools: search_vessels, get_vessel, vessels_in_area, vessels_near, vessel_track, and 16 more. Their descriptions and schemas cost roughly 3,293 tokens of context every time the server is loaded.

Does the Gangway AIS MCP server require authentication?

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

Is the Gangway AIS MCP server still maintained?

Gangway AIS is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Gangway AIS MCP server?

VerifyMCP ran 13 checks on Gangway AIS, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.