Open Waters AIS MCP server
io.openwaters/aisopenwaters.iostreamable-httpv0.18.3Scanned
Live AIS vessel positions by MMSI, name, area, or radius, plus coverage. No sign-in, no key.
6 tools: 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Open Waters AIS MCP server can do
The Open Waters AIS MCP server is published by openwaters.io, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.18.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Only reads 6Show 6 read-only tools
find_vessels_in_areaVessels currently inside a latitude/longitude bounding box, newest report first, with optional kind and ship-type filters.No findings
Why it is in this group
- The name "find_vessels_in_area" says "find": a word for reading.
Description, as the server wrote it Vessels currently inside a latitude/longitude bounding box, newest report first, with optional kind and ship-type filters. Anonymous calls may cover 100 square degrees per call.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Vessels in an area
find_vessels_nearVessels 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.No findings
Why it is in this group
- The name "find_vessels_near" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Vessels near a point or vessel
get_coverageWhere Open Waters AIS is hearing AIS right now: sources with their current delay, stations, freshness, and vessel counts.No findings
Why it is in this group
- The name "get_coverage" says "get": a word for reading.
Description, as the server wrote it Where Open Waters AIS is hearing AIS right now: sources with their current delay, stations, freshness, and vessel counts. A bounding box adds the stations whose coverage overlaps that area and a count of vessels in it. A station ID adds statistics for that station. 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. An area without reports may have gaps in coverage.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Coverage and sources
get_vessel_trackThe positions heard from one vessel over a time range, oldest first, with speed, course, and navigational status.No findings
Why it is in this group
- The name "get_vessel_track" says "get": a word for reading.
Description, as the server wrote it 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. A vessel can be identified by MMSI, or by IMO with a feeder or partner token. 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Where a vessel has been
get_vesselsLast known position and particulars of specific vessels by MMSI (Maritime Mobile Service Identity), or by IMO number with a feeder or partner token: the last report heard for each,…No findings
Why it is in this group
- The name "get_vessels" says "get": a word for reading.
Description, as the server wrote it Last known position and particulars of specific vessels by MMSI (Maritime Mobile Service Identity), or by IMO number with a feeder or partner token: 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Vessels by MMSI
search_vessels_by_nameVessels whose name contains the text, case-insensitive, among every vessel the network has heard, each with its MMSI and last known position when available.No findings
Why it is in this group
- The name "search_vessels_by_name" says "search": a word for reading.
Description, as the server wrote it Vessels whose name contains the text, case-insensitive, among every vessel the network has heard, each with its MMSI and last known position when available. An optional bounding box narrows the search. With a feeder or partner token, text of the form IMO 9241061 finds the vessels reporting that IMO number, and a bare seven-digit number finds them ahead of the name matches.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Search vessels by name
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:14 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools6 changed.~6 changedView diff
- Changed:find_vessels_in_areaOnly readsannotations
- Changed:find_vessels_nearOnly readsannotations
- Changed:get_coverageOnly readsannotations
- Changed:get_vessel_trackOnly readsannotations
- Changed:get_vesselsOnly readsannotations
- Changed:search_vessels_by_nameOnly readsannotations
Tools6 changed.~6 changedView diff
- Changed:find_vessels_in_areaOnly readsdescription
- Changed:find_vessels_nearOnly readsdescriptioninputSchema
- Changed:get_coverageOnly readsdescriptioninputSchema
- Changed:get_vessel_trackOnly readsdescriptioninputSchema
- Changed:get_vesselsOnly readsdescription
- Changed:search_vessels_by_nameOnly readsdescription
Install
Pinned to version 0.18.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http ais https://ais.openwaters.io/mcpclaude mcp add --transport http ais https://ais.openwaters.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ais__find_vessels_in_area",
"mcp__ais__find_vessels_near",
"mcp__ais__get_coverage",
"mcp__ais__get_vessel_track",
"mcp__ais__get_vessels",
"mcp__ais__search_vessels_by_name"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ais. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.openwaters/ais/verify?hash=fe52c8c3006e21fe43417549b2867a03b2f36af78ef9152a8979d179c6a63f7c" | jq -e '.changed == false'Pinned hash fe52c8c3006e, from Nov 16, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.openwaters/ais/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.openwaters/ais)Source: MCP Registry · repository. Synced Nov 16, 2026, 01:18 UTC.
Open Waters AIS MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Open Waters AIS MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Open Waters AIS MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Open Waters AIS MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Open Waters AIS MCP server have?
- 6 tools: 6 read. find_vessels_in_area, find_vessels_near, get_coverage, get_vessel_track, get_vessels and search_vessels_by_name.
Does the Open Waters AIS MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Open Waters AIS MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Open Waters AIS MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.