Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Open Waters AIS is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Live AIS vessel positions by MMSI, name, area, or radius, plus coverage. No sign-in, no key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http open-waters-ais-mcp https://ais.openwaters.io/mcp
# 2 — ask your agent for something these tools do
# find_vessels_in_area, find_vessels_near, get_coverage and 3 more
Open Waters AIS costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
OPAll 1 server
openwaters1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http open-waters-ais-mcp https://ais.openwaters.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bbox | object | yes | — |
| kind | string | no | only this kind: vessel, aton (aid to navigation), base (base station), sar (search and rescue aircraft or distress beacon), or gear (fishing gear); vessel leaves out distress beacons and gear |
| flag | string | no | only vessels flying this flag: ISO 3166-1 alpha-2, e.g. NO, FI, MH |
| types | null/array | no | 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 |
| limit | integer | no | rows to return: default 50, maximum 200 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | null/number | no | centre latitude, degrees; give lat and lon, or mmsi |
| lon | null/number | no | centre longitude, degrees |
| mmsi | integer | no | centre on this vessel's last position instead of lat and lon; the vessel itself is left out of the results |
| radius_nm | number | no | search radius in nautical miles: default 10, maximum 50 |
| kind | string | no | only this kind: vessel, aton, base, sar, or gear; vessel leaves out distress beacons and gear |
| flag | string | no | only vessels flying this flag: ISO 3166-1 alpha-2, e.g. NO, FI, MH |
| types | null/array | no | only these ITU ship type codes; a code ending in 0 matches its decade |
| limit | integer | no | rows to return: default 50, maximum 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bbox | null/object | no | report the stations covering this box and the vessels currently in it |
| station | string | no | a station id from an earlier result, for that station's numbers |
| max_age | string | no | 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 |
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. Give the vessel's mmsi, or its imo with a feeder or partner token. A call covers up to a year. By default the track is simplified by shape: the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mmsi | integer | no | the vessel's MMSI; give mmsi or imo. Use search_vessels_by_name first when you only have a name |
| imo | integer | no | the vessel's IMO number, instead of mmsi; needs a feeder or partner token. Follows the one vessel the IMO names: its only MMSI, or the only one heard in the last 30 days |
| from | string | no | start, RFC 3339 UTC; default 24 hours before to. A call covers up to 366 days |
| to | string | no | end, RFC 3339 UTC; default now |
| interval_minutes | integer | no | 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 | no | positions to return: default 50, maximum 200; when more match, the newest are kept |
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 carri
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mmsi | null/array | no | MMSIs to look up; anonymous calls may pass 10 identifiers per call, a personal token 50 |
| imo | null/array | no | IMO numbers to look up, counted with mmsi against the same cap; needs a feeder or partner token. Each returns up to 10 vessels that reported it, most recently heard first, and a vessel is found by IMO |
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. 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 fin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | text to find in the vessel name, at least 2 characters, case-insensitive; with a feeder or partner token, IMO followed by an IMO number finds that IMO |
| bbox | null/object | no | only vessels whose last position is inside this box |
| flag | string | no | only vessels flying this flag: ISO 3166-1 alpha-2, e.g. NO, FI, MH |
| limit | integer | no | rows to return: default 50, maximum 200 |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Open Waters AIS or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.17.0.
0.17.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Open Waters AIS can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.