# Gangway AIS (remote · gangwayais.com)

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

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gangwayais.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-gangwayais-ais/gangwayais.md), [page](https://verifymcp.io/servers/com-gangwayais-ais/gangwayais)

## Channel facts

- Endpoint: `https://gangwayais.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

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

### Claude

```bash
claude mcp add --transport http com-gangwayais-ais 'https://gangwayais.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-gangwayais-ais": {
      "url": "https://gangwayais.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gangwayais-ais": {
      "type": "http",
      "url": "https://gangwayais.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-gangwayais-ais]
url = "https://gangwayais.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gangwayais-ais": {
      "type": "remote",
      "url": "https://gangwayais.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gangwayais-ais --url 'https://gangwayais.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-gangwayais-ais:
    url: "https://gangwayais.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-gangwayais-ais": {
      "Transport": "http",
      "Url": "https://gangwayais.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gangwayais-ais -t streamable-http -u 'https://gangwayais.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-gangwayais-ais": {
      "type": "http",
      "url": "https://gangwayais.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 75, +1)

- [security] 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

### 2026-11-20 (score 74, 0)

- [cosmetic] “port_events” reworded the description of “kinds”

### 2026-11-19 (score 74, +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.

### 2026-11-18 (score 73, 0)

- [security] 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

### 2026-11-16 (score 73, +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.

### 2026-11-15 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 72)

First indexed and scored.

## MCP tools (21)

### `search_vessels` (~182 tokens)

Search vessels

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.

Input parameters:

- `limit` (integer): At most this many vessels (default 10)
- `near_lat` (number): Optional: rank vessels near this latitude first
- `near_lon` (number): Optional: rank vessels near this longitude first
- `query` (string, required): Name, MMSI or IMO, or the start of one

### `get_vessel` (~157 tokens)

Vessel now

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.

Input parameters:

- `imo` (integer): The vessel's IMO number, seven digits
- `mmsi` (integer): The vessel's MMSI, nine digits

### `vessels_in_area` (~263 tokens)

Vessels in an area

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.

Input parameters:

- `limit` (integer): At most this many vessels (default 50)
- `max_age` (string): Only vessels heard within this time, such as 90m, 24h or 7d (default 24h)
- `max_lat` (number, required): North edge of the box
- `max_lon` (number, required): East edge of the box
- `min_lat` (number, required): South edge of the box
- `min_lon` (number, required): West edge of the box
- `min_speed_kn` (number): Only vessels at or above this speed over ground, in knots
- `ship_type` (integer): AIS ship type: a code ending in 0 means its whole group (70 all cargo, 80 all tankers)

### `vessels_near` (~248 tokens)

Vessels near a point or vessel

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.

Input parameters:

- `lat` (number): Latitude in decimal degrees, north positive
- `limit` (integer): At most this many vessels (default 25)
- `lon` (number): Longitude in decimal degrees, east positive
- `max_age` (string): Only vessels heard within this time, such as 90m or 24h (default 24h)
- `mmsi` (integer): Or centre on this vessel's last position
- `radius_nm` (number): Radius in nautical miles (default 10, at most 30)

### `vessel_track` (~201 tokens)

Where a vessel has been

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

Input parameters:

- `from` (string): Start, ISO 8601 UTC such as 2026-11-01T00:00:00Z
- `hours` (integer): Hours back from now
- `max_points` (integer): Hand back at most this many points (default 300)
- `mmsi` (integer, required): The vessel's MMSI, nine digits
- `to` (string): End, ISO 8601 UTC (default now)

### `vessel_port_calls` (~141 tokens)

A vessel's port calls

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

Input parameters:

- `days` (integer): Days back from now (default 7)
- `mmsi` (integer, required): The vessel's MMSI, nine digits

### `vessel_activity` (~132 tokens)

A vessel's activity

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

Input parameters:

- `days` (integer): Days back from now (default 30)
- `mmsi` (integer, required): The vessel's MMSI, nine digits

### `sanctions_check` (~119 tokens)

Sanctions check

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

Input parameters:

- `imo` (integer, required): The vessel's IMO number, seven digits with a valid check digit

### `search_ports` (~133 tokens)

Search ports

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.

Input parameters:

- `limit` (integer): At most this many ports (default 8)
- `near_lat` (number): Or: the ports nearest this latitude
- `near_lon` (number): Or: the ports nearest this longitude
- `query` (string): A port name or UN/LOCODE

### `resolve_destination` (~86 tokens)

Which port a destination means

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.

Input parameters:

- `destination` (string, required): The destination as the vessel broadcasts it

### `port_now` (~138 tokens)

Port now

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.

Input parameters:

- `limit` (integer): At most this many vessels in each list (default 40)
- `port` (string, required): A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

### `port_vessels` (~200 tokens)

Expected, in port, arrived, departed

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

Input parameters:

- `flag` (string): Only this flag, a two-letter ISO country code
- `kind` (string): Only this kind of vessel
- `limit` (integer): At most this many vessels (default 50)
- `list` (string): Which list (default expected)
- `max_length_m` (number): Only vessels at most this long, in metres
- `min_length_m` (number): Only vessels at least this long, in metres
- `port` (string, required): A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

### `port_waiting_times` (~123 tokens)

Waiting times at anchor

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

Input parameters:

- `include_vessels` (boolean): Also list the vessels at anchor now (default false)
- `port` (string, required): A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

### `port_calls_on_date` (~122 tokens)

Calls on a day

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

Input parameters:

- `date` (string): The day, YYYY-MM-DD (UTC)
- `port` (string, required): A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

### `port_congestion` (~129 tokens)

Port congestion

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

Input parameters:

- `days` (integer): Days back from now (default 30)
- `port` (string, required): A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)

### `port_events` (~259 tokens)

Port events

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

Input parameters:

- `kinds` (string): Comma-separated kinds, or "all". Kinds: aground, aisoff, anchored, approaching, arrived, bunkering, delayrisk, destination, dragging, draught, drifting, eta, heard, left, pilot, quiet, renamed, slow,…
- `limit` (integer): At most this many events (default 60)
- `max_lat` (number): North edge of the box
- `max_lon` (number): East edge of the box
- `min_lat` (number): South edge of the box
- `min_lon` (number): West edge of the box
- `since` (string): ISO 8601 UTC time to start from

### `plan_route` (~184 tokens)

Plan a passage

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

Input parameters:

- `draught_m` (number): Her draught in metres
- `from_lat` (number, required): Latitude in decimal degrees, north positive
- `from_lon` (number, required): Longitude in decimal degrees, east positive
- `length_m` (number): Her length overall in metres
- `to_lat` (number, required): Latitude in decimal degrees, north positive
- `to_lon` (number, required): Longitude in decimal degrees, east positive

### `check_route` (~219 tokens)

Check a passage

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

Input parameters:

- `air_draught_m` (number): Her air draught in metres
- `beam_m` (number): Her beam in metres
- `draught_m` (number): Her draught in metres
- `length_m` (number): Her length overall in metres
- `sea_room_nm` (number): Sea room to keep off danger, in nautical miles
- `ukc_m` (number): Under-keel clearance to keep, in metres
- `waypoints` (array, required): The route's turning points in order, each [lat, lon]

### `depth_at` (~105 tokens)

Depth at a position

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

Input parameters:

- `lat` (number, required): Latitude in decimal degrees, north positive
- `lon` (number, required): Longitude in decimal degrees, east positive

### `account_usage` (~77 tokens)

Credits and plan

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.

### `data_sources` (~75 tokens)

Data sources

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-gangwayais-ais/gangwayais#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72
- 2026-11-14: 72

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

## Links

- Remote endpoint: https://gangwayais.com/mcp
- Authorisation metadata: https://gangwayais.com/.well-known/oauth-protected-resource/mcp
- Website: https://gangwayais.com/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-gangwayais-ais/gangwayais.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gangwayais-ais/gangwayais/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-gangwayais-ais/gangwayais.json
- HTML version of this page: https://verifymcp.io/servers/com-gangwayais-ais/gangwayais
