Open Waters AIS
REMOTE · AIS.OPENWATERS.IO · SCANNED OCT 4
Live AIS vessel positions by MMSI, name, area, or radius, plus coverage. No sign-in, no key.
Available components
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
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2051 tokens (~341/item across 6 items; 6 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the Open Waters AIS MCP server?
Open Waters AIS is a hosted endpoint at https://ais.openwaters.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 · ais.openwaters.io
claude mcp add --transport http io-openwaters-ais 'https://ais.openwaters.io/mcp'
{
"mcpServers": {
"io-openwaters-ais": {
"url": "https://ais.openwaters.io/mcp"
}
}
} {
"servers": {
"io-openwaters-ais": {
"type": "http",
"url": "https://ais.openwaters.io/mcp"
}
}
} [mcp_servers.io-openwaters-ais] url = "https://ais.openwaters.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-openwaters-ais": {
"type": "remote",
"url": "https://ais.openwaters.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-openwaters-ais --url 'https://ais.openwaters.io/mcp' --transport streamable-http
mcp_servers:
io-openwaters-ais:
url: "https://ais.openwaters.io/mcp" {
"McpServers": {
"io-openwaters-ais": {
"Transport": "http",
"Url": "https://ais.openwaters.io/mcp"
}
}
} assistant mcp add io-openwaters-ais -t streamable-http -u 'https://ais.openwaters.io/mcp'
{
"mcpServers": {
"io-openwaters-ais": {
"type": "http",
"url": "https://ais.openwaters.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_vessel_track” rewrote its description, which is the text the model reads security
- Server version: 0.9.0 → 0.11.0 functional
- “get_vessel_track” reworded the description of “from” cosmetic
- 2 Oct 26 0
- Server version: 0.8.0 → 0.9.0 functional
- 1 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_vessels” rewrote its description, which is the text the model reads security
- Tool “get_coverage” rewrote its description, which is the text the model reads security
- Schema quality: 273 → 339 ▼ functional
- Server version: 0.7.0 → 0.8.0 functional
- Server version: 0.6.0 → 0.7.0 functional
- “get_coverage” added an optional parameter “max_age” cosmetic
- 30 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_vessel_track” rewrote its description, which is the text the model reads security
- Server version: 0.5.2 → 0.6.0 functional
- “get_vessel_track” reworded the description of “from” cosmetic
- “get_vessel_track” reworded the description of “interval_minutes” cosmetic
- 29 Sept 26 +1
- Tool “get_vessel_track” rewrote its description, which is the text the model reads security
- Server version: 0.5.1 → 0.5.2 functional
- 28 Sept 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_vessels_near” rewrote its description, which is the text the model reads security
- Schema quality: 1284 → 1577 ▼ functional
- Schema quality: 1284 → 1573 ▼ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 0.5.0 → 0.5.1 functional
- Server version: 0.4.0 → 0.5.0 functional
- New tool “get_vessel_track” functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 7 Oct 2026 · Probed https://ais.openwaters.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ais.openwaters.io | CN=YE2,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 57219dc3c043fddd7e3e8d38d51f8e51143 |
| SANs: ais.openwaters.io | ||||||
| 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 ais.openwaters.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| openwaters.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ais.openwaters.io/mcp | Verified | 200 | |
| http (plaintext) | http://ais.openwaters.io/mcp | HTTPS enforced | 308 | https://ais.openwaters.io/mcp |
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 →
find_vessels_in_area Vessels in an area ~221
Vessels currently inside a latitude/longitude bounding box, newest report first, with optional kind and ship-type filters. Use for what is in a port, a strait, or a stretch of coast. Anonymous calls may cover 100 square degrees per call.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | object | yes | – |
| flag | string | – | only vessels flying this flag: ISO 3166-1 alpha-2, e.g. NO, FI, MH |
| kind | string | – | only this kind: vessel, aton (aid to navigation), base (base station), or sar (search and rescue aircraft) |
| limit | integer | – | rows to return: default 50, maximum 200 |
| types | null|array | – | only these ITU ship type codes, e.g. 30 fishing, 36 sailing, 37 pleasure craft, 52 tug, 60 passenger, 70 cargo, 80 tanker; a code ending in 0 matches its decade, so 70 matches 70 to 79 |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | credit line per source kind in the rows, to show with the data |
| total | integer | yes | vessels matched before the limit was applied |
| truncated | boolean | yes | true when total exceeds the rows returned; narrow the query or raise limit |
| unknown_imo | null|array | – | requested IMO numbers matching no vessel the network has heard |
| unknown_mmsi | null|array | – | requested MMSIs matching no vessel the network has heard |
| vessels | null|array | yes | – |
No examples provided.
find_vessels_near Vessels near a point or vessel ~249
Vessels within a radius (default 10 NM, maximum 50) of a point or of another vessel's last known position, nearest first, each with distance and bearing from the centre. Use for what is near this position or what is around vessel X.
| Name | Type | Req | Description |
|---|---|---|---|
| flag | string | – | only vessels flying this flag: ISO 3166-1 alpha-2, e.g. NO, FI, MH |
| kind | string | – | only this kind: vessel, aton, base, or sar |
| lat | null|number | – | centre latitude, degrees; give lat and lon, or mmsi |
| limit | integer | – | rows to return: default 50, maximum 200 |
| lon | null|number | – | centre longitude, degrees |
| mmsi | integer | – | centre on this vessel's last position instead of lat and lon; the vessel itself is left out of the results |
| radius_nm | number | – | search radius in nautical miles: default 10, maximum 50 |
| types | null|array | – | only these ITU ship type codes; a code ending in 0 matches its decade |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | credit line per source kind in the rows, to show with the data |
| total | integer | yes | vessels matched before the limit was applied |
| truncated | boolean | yes | true when total exceeds the rows returned; narrow the query or raise limit |
| unknown_imo | null|array | – | requested IMO numbers matching no vessel the network has heard |
| unknown_mmsi | null|array | – | requested MMSIs matching no vessel the network has heard |
| vessels | null|array | yes | – |
No examples provided.
get_coverage Coverage and sources ~200
Where Open Waters AIS is hearing AIS right now: sources with their current delay, stations, freshness, and vessel counts. Pass a bounding box to learn which stations cover it and how many vessels are in it, or a station id for that station's numbers. Vessel counts cover the last 30 minutes; max_age widens them, to 7d for the last week or all for every vessel the network has heard. Call this before saying a region has no traffic.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | null|object | – | report the stations covering this box and the vessels currently in it |
| max_age | string | – | count vessels heard within this long, network-wide and in bbox, instead of the last 30 minutes: a duration such as 6h, 24h, or 7d, or all for every vessel the network has heard |
| station | string | – | a station id from an earlier result, for that station's numbers |
| Name | Type | Req | Description |
|---|---|---|---|
| area | null|object | – | – |
| events_per_second | number | yes | – |
| note | string | – | – |
| sources | null|array | yes | – |
| station | null|object | – | – |
| stations | object | yes | – |
| summary | string | yes | – |
| time | string | yes | – |
| vessels | object | yes | – |
No examples provided.
get_vessel_track Where a vessel has been ~260
The positions heard from one vessel over a time range, oldest first, with speed, course, and navigational status. Positions implying an impossible speed for the vessel are left out. Use for where a ship was yesterday, when it left port, or its route today. A call covers up to a year. By default the track is simplified by shape: the positions that hold its path, with breaks where the vessel went unheard; interval_minutes asks for even spacing instead.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | start, RFC 3339 UTC; default 24 hours before to. A call covers up to 366 days |
| interval_minutes | integer | – | at most one position per this many minutes, evenly spaced; by default the track is simplified by shape instead, keeping the positions that hold its path. Anonymous and personal calls reaching past 48… |
| limit | integer | – | positions to return: default 50, maximum 200; when more match, the newest are kept |
| mmsi | integer | yes | the vessel's MMSI; use search_vessels_by_name first when you only have a name |
| to | string | – | end, RFC 3339 UTC; default now |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | credit line per source kind in the positions, to show with the data |
| breaks | null|array | – | simplified, always present and empty when the vessel was heard throughout: indexes of positions that start a stretch after it went unheard; draw no line into them |
| from | string | yes | start of the range covered |
| interval_s | integer | yes | at most one position per this many seconds; 0 is every position heard. Simplified, the resolution the positions were read at |
| mmsi | integer | yes | – |
| name | string | – | – |
| positions | null|array | yes | oldest first |
| simplified | boolean | yes | true when the track was simplified by shape: the positions that hold its path, not evenly spaced |
| to | string | yes | – |
| tolerance_m | null|number | – | simplified: every position left out lay within this many meters of the line through the ones kept |
| truncated | boolean | yes | true when positions were left out: simplified, the tolerance rose past 15 m to fit the limit, or the range held more than 50,000 positions and the oldest were not read; by interval, the newest were k… |
No examples provided.
get_vessels Vessels by MMSI ~230
Last known position and particulars of specific vessels by MMSI (Maritime Mobile Service Identity) or IMO number: the last report heard for each, however long ago, with destination, ETA, draught, and dimensions once its static data has been heard, and which identifiers match no vessel the network has heard. A vessel whose IMO number has a Wikidata item also carries its type, builder, year built, tonnage, registered dimensions, registry, home port, owner, operator, former names, and Wikipedia and Commons links from there, and a documented US vessel its service type, status, official number, registered dimensions, and tonnage from the US Coast Guard. Use search_vessels_by_name first when you only have a name.
| Name | Type | Req | Description |
|---|---|---|---|
| imo | null|array | – | IMO numbers to look up, counted with mmsi against the same cap; a vessel is found by IMO only once its static data has been heard |
| mmsi | null|array | – | MMSIs to look up; anonymous calls may pass 10 identifiers per call, a personal token 50 |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | credit line per source kind in the rows, to show with the data |
| total | integer | yes | vessels matched before the limit was applied |
| truncated | boolean | yes | true when total exceeds the rows returned; narrow the query or raise limit |
| unknown_imo | null|array | – | requested IMO numbers matching no vessel the network has heard |
| unknown_mmsi | null|array | – | requested MMSIs matching no vessel the network has heard |
| vessels | null|array | yes | – |
No examples provided.
search_vessels_by_name Search vessels by name ~165
Vessels whose name contains the text, case-insensitive, among every vessel the network has heard, each with its last known position. Use to turn a name into an MMSI, then get_vessels or find_vessels_near for detail. An optional bounding box narrows the search.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | null|object | – | only vessels whose last position is inside this box |
| flag | string | – | only vessels flying this flag: ISO 3166-1 alpha-2, e.g. NO, FI, MH |
| limit | integer | – | rows to return: default 50, maximum 200 |
| name | string | yes | text to find in the vessel name, at least 2 characters, case-insensitive |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | credit line per source kind in the rows, to show with the data |
| total | integer | yes | vessels matched before the limit was applied |
| truncated | boolean | yes | true when total exceeds the rows returned; narrow the query or raise limit |
| unknown_imo | null|array | – | requested IMO numbers matching no vessel the network has heard |
| unknown_mmsi | null|array | – | requested MMSIs matching no vessel the network has heard |
| vessels | null|array | yes | – |
No examples provided.
What is the Open Waters AIS MCP server?
Open Waters AIS is an MCP server listed in the public MCP registry as io.openwaters/ais. Live AIS vessel positions by MMSI, name, area, or radius, plus coverage. No sign-in, no key. This page covers its hosted endpoint (https://ais.openwaters.io/mcp).
Is the Open Waters AIS MCP server safe to use?
Open Waters AIS scores 76 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 Open Waters AIS MCP server expose?
Open Waters AIS exposes 6 tools: find_vessels_in_area, find_vessels_near, get_coverage, get_vessel_track, get_vessels, search_vessels_by_name. Their descriptions and schemas cost roughly 1,325 tokens of context every time the server is loaded.
Does the Open Waters AIS MCP server require authentication?
No. We connected to Open Waters AIS without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Open Waters AIS MCP server still maintained?
Open Waters AIS is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.