Open Waters AIS

io.openwaters由 openwaters.io 发布官方发布者v0.18.2更新于 Nov 8, 2026

Live AIS vessel positions by MMSI, name, area, or radius, plus coverage. No sign-in, no key.

已验证Streamable HTTP可网页运行位置与生活数据与分析

概览

AI 生成的概览

以只读方式查询 Open Waters AIS 网络的实时船舶位置、航迹、船舶资料与接收覆盖,可按区域、半径、船名或 MMSI 检索。

可以做什么
  • 按经纬度范围或按某点、某船周围的半径查找船舶,按距离由近到远并给出方位。
  • 按 MMSI 查询指定船舶的最后位置、目的地、预计到达时间、吃水与尺寸,并合并登记资料。
  • 按船名搜索船舶,可限定在某个区域内。
  • 获取某艘船在一段时间内的位置历史,单次最多一年。
  • 查看网络当前的 AIS 接收情况,包括各数据源的延迟、站点与船舶数量。
适用场景
适合让助手回答当前或过去的船舶交通问题,例如某港口或坐标附近有哪些船、某艘具名船最后在哪里被收到、某区域的覆盖是否新鲜。适用于研究、监测与态势了解,而非实际航行操作。
运行要求
远程 MCP 端点,使用 streamable HTTP;匿名使用无需登录或密钥。匿名调用每次限 100 平方度、每次查询 10 艘船。免费个人令牌通过 Authorization: Bearer 请求头发送可提高限额;按 IMO 号查询船舶需要 feeder 或 partner 令牌。
安装前请注意
工具为只读,但数据覆盖不均、处于 beta 且无 SLA,某区域没有报告可能只是覆盖缺口。结果中的署名信息在展示数据时必须保留,各数据源许可不同,部分来源的再分发条款尚未确定。不能替代船载 AIS,也不可用于航行安全。放在 Authorization 请求头中的令牌属于凭据,需妥善保管。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Open Waters AIS,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.openwaters%2Fais/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "open-waters-ais": {
      "type": "http",
      "url": "https://ais.openwaters.io/mcp"
    }
  }
}

README

aiscast

Live AIS vessel traffic, streamed by bounding box, from community networks, open government feeds, and volunteer receivers. Part of Open Waters. The public instance is ais.openwaters.io. A live map is at openwaters.io/ais/vessels.

This is a beta. There is no SLA. Coverage is uneven. The terms for re-serving some sources are still unsettled (see Coverage). Live status and uptime history are at status.openwaters.io.

Usage

aisstream.io clients. aiscast speaks aisstream.io's protocol on wss://ais.openwaters.io/v0/stream: the same subscribe message, the same MessageType / MetaData / Message frames. Change the hostname and use your aiscast token as the APIKey. Existing code keeps working: aisstream-ts, the official Go/Python/JS examples, and signalk-aisstream.

Native API (full reference).

  • wss://ais.openwaters.io/v1/stream: send {"type":"subscribe","bbox":[[minLat,minLon,maxLat,maxLon]]} or {"type":"subscribe","mmsi":[368168720]} (or both). Feeder and partner tokens can also follow vessels by IMO number with "imo":[9241061]. You receive one JSON event per decoded AIS message. Each event carries its source, station, receive time, raw sentence, and the decoded fields. Add "snapshot":true to get the last known messages for every vessel already tracked in the subscription first, then live traffic. Subscribing needs no token.
  • GET https://ais.openwaters.io/v1/vessels?bbox=minLat,minLon,maxLat,maxLon (or ?mmsi=a,b,c): GeoJSON of every vessel currently in view. Each vessel carries its last position, name, type, course, speed, heading, flag, and when and from where aiscast last heard it, plus IMO number, call sign, destination, ETA, draught, length, beam, and the AIS antenna's distances to bow, stern, port, and starboard once its static data has been heard. No token.
  • GET https://ais.openwaters.io/v1/stations: every source aiscast is hearing, with message counts and age.

AI assistants. https://ais.openwaters.io/mcp is an MCP (Model Context Protocol) server with five read-only tools: vessels by MMSI, vessels in an area, vessels near a point or another vessel, search by name, and coverage. No sign-in. Claude Code: claude mcp add --transport http open-waters-ais https://ais.openwaters.io/mcp. Claude.ai, ChatGPT, Cursor, and VS Code take the URL as a custom connector or mcp.json entry; setup for each is in the API reference. A token in an Authorization: Bearer header raises the anonymous limits.

Tokens. /v0/stream needs a token. A personal token is self-serve and never expires. Use the token page, or generate an Ed25519 keypair and POST https://ais.openwaters.io/v1/keys with {"pubkey":"<base64url public key>"}, signed with that key as the API reference shows. The response is your token. It carries the personal tier: 2 streams, 50 messages/s, and a 20°×20° area. Feed data from the same token and it becomes a feeder token by itself.

Tiers and limits are in docs/limits.md. For more than the feeder tier, or for commercial use, write to [email protected].

Events carry a source, so you can tell a live volunteer receiver from a government feed or an aggregate. synthesized: true marks messages that aiscast re-encoded from a non-NMEA source.

Contributing data

If you run an AIS receiver, send its data here. aiscast re-serves it to everyone, deduplicates it against the open feeds and every other station, and shares volunteer receptions with AISHub as part of our contribution to its community network. Only data received directly by volunteer stations goes to AISHub; public feeds and synthesized messages stay out. You are welcome to keep contributing to other networks too. The terms for contributing are the contributor agreement.

  • AIS-catcher (preferred: authenticated, realtime, works behind any NAT): get a token at openwaters.io/ais/token (one click, stays in your browser), then AIS-catcher ... -Q wssmqtt://x:<token>@ais.openwaters.io:443/v1/stream MSGFORMAT NMEA. Each message is sent as it is decoded, over MQTT on the same WebSocket address the JSON stream uses. Your data appears as source: station:<station id>. Name your station on the token page; until you do, it is labeled by the town nearest the traffic it hears. AIS-catcher's HTTP output works too: -H https://ais.openwaters.io/v1/receive USERPWD x:<token> GZIP on INTERVAL 5 posts a batch every five seconds under the same station.
  • UDP (no token): AIS-catcher -u udp.ais.openwaters.io 10110, docker-shipfeeder with host udp.ais.openwaters.io port 10110, or any NMEA forwarder sending plain !AIVDM / !AIVDO sentences (TAG blocks welcome). Your station appears as udp:<id>, a keyed hash of your address, never the address itself. If a sender's !AIVDO sentences identify the vessel, aiscast keys the station by that MMSI instead.
  • Signal K: add a UDP target udp.ais.openwaters.io:10110 in ais-forwarder (forward AIVDM and AIVDO). Or install the signalk-aiscast plugin. It needs no token. It shares what your receiver hears, and your own position, taken from the transponder or built from Signal K when an AIS transponder is not available. It shows aiscast traffic when you have no receiver.

Your station page is https://openwaters.io/ais/stations/<your id>, and the station list links every station. It shows the station's uptime, its messages per hour over the last week, the vessels it heard in the last day by type and how many no other station heard, and the cells it heard over the last week on the map. GET /v1/stations/{id} and /v1/coverage/tiles.json?station=<id> return the same figures. Feeders get the deduplicated raw stream back on wss://ais.openwaters.io/v1/nmea.

Coverage

SourceWhereFreshness
KystverketNorwegian coast, 40–60 nm outlive
BarentsWatchNorwegian EEZ, Svalbard, Jan Mayen (satellite + offshore receivers)live
Fintraffic DigitrafficFinnish waterslive
Volunteer receiverswherever they are (Buzzards Bay / Vineyard Sound as of the first station)live
AISHub aggregateworldwide terrestrial, ~50k vesselsabout a minute behind
aisstream.ioworldwide, when it is uplive, but frequently down

AISHub and its contributors make much of our worldwide terrestrial coverage possible. We contribute volunteer receptions in return and credit AISHub on every event from its aggregate.

/v1/stats reports each source's current delay from broadcast to arrival (delay.p50 and delay.p99, in seconds).

Every event names the source it came from. docs/policy.md lists the sources this project leaves out on purpose, and why.

Licensing and attribution

Licensing is per source. aiscast does not relicense the aggregate. aiscast re-serves each event under the terms of the source it came from. That is why source is on every event, every vessel, and every archived hour, and why every /v1 event carries a license tag and an attribution credit line. Every attribution opens with "Open Waters AIS (https://openwaters.io/ais/)"; sources with their own terms add their credit after it. If you display or redistribute the data, display the attribution message included with each event. /v1/vessels carries the same credits as a top-level attribution member on the feature collection, one entry per source present. The table below is the same information as reference.

SourceLicenseWhat you must do
KystverketNLOD 2.0Credit: "Contains data under the Norwegian licence for Open Government data (NLOD) distributed by the Norwegian Coastal Administration." NLOD is not sublicensable, so it binds you directly.
BarentsWatchNLOD per the BarentsWatch API termsCredit: "Data delivered by BarentsWatch." It is the same AIS Norge data as Kystverket, so the Kystverket credit applies too.
Fintraffic DigitrafficCC BY 4.0Credit: "Source: Fintraffic / digitraffic.fi, license CC 4.0 BY."
Volunteer receiversThe contributor agreement dedicates receptions to the public domain under CC0 and publishes the aggregate under ODbLCredit "Open Waters AIS (https://openwaters.io/ais/)". Individual receptions are CC0. The aggregate carries ODbL.
AISHub aggregateAISHub terms and any applicable written agreementCredit AISHub contributors and keep source: aishub. Reuse and redistribution must follow the applicable terms.
aisstream.iono published termsBest effort, may disappear. source: aisstream.
Wikidata particularsCC0 1.0Nothing. The wikidata object on /v1/vessels/{mmsi} and in MCP get_vessels says so with license: CC0-1.0. The Commons photos its image and commons_category link to carry their own licenses.
US Coast Guard PSIXPublic domain (U.S. government work)Nothing. The uscg object on /v1/vessels/{mmsi} and in MCP get_vessels says so in its license.
AMSA ship registerCC BY 4.0Credit: "© Australian Maritime Safety Authority". The sources.amsa entry on /v1/vessels/{mmsi} and in MCP get_vessels carries it with license: CC-BY-4.0.
MarineCadastrePublic domain (U.S. government work); NOAA labels its 2024 release CC0Nothing required. Track history from it credits "U.S. Coast Guard Nationwide AIS, via MarineCadastre.gov (NOAA and BOEM)." and keeps source: marinecadastre.
Danish Maritime AuthorityReuse under the Danish public sector information act; the data management policy forbids combining it so that private individuals become identifiableTrack history from it credits "Danish Maritime Authority." and keeps source: dma.

aiscast's own code is MIT. aiscast identifies UDP stations by a keyed hash instead of an address (a station that sends !AIVDO is keyed by that MMSI, and its position is in the data it shares). Station labels on /v1/stations, and near on vessel searches and /v1/vessels/{mmsi}, name the nearest town from GeoNames, CC BY 4.0. The archive keeps raw receptions per source, so the project can purge any source. docs/policy.md states the full position: what the contributor agreement says, the privacy rules, and how the project intends to fund itself without relicensing data.

Contributing

Developers and operators: see CONTRIBUTING.md.

来源:README.md,提交 55aa9b4

工具

6

find_vessels_in_area

Vessels in an area

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.

输入参数bbox必填flagkindlimittypes

find_vessels_near

Vessels near a point or vessel

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.

输入参数latlonflagkindmmsilimittypesradius_nm

get_coverage

Coverage and sources

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.

输入参数bboxmax_agestation

get_vessel_track

Where a vessel has been

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.

输入参数toimofrommmsilimitinterval_minutes

get_vessels

Vessels by MMSI

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.

输入参数imommsi

search_vessels_by_name

Search vessels by name

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.

输入参数bboxflagname必填limit

版本历史

19
  1. v0.18.1Nov 7, 2026
  2. v0.18.0Oct 23, 2026
  3. v0.17.0Oct 10, 2026
  4. v0.16.0Oct 9, 2026
  5. v0.15.0Oct 8, 2026
  6. v0.14.0Oct 8, 2026
  7. v0.13.0Oct 7, 2026
  8. v0.12.0Oct 6, 2026
  9. v0.11.0Oct 3, 2026
  10. v0.9.0Oct 2, 2026
  11. v0.8.0Oct 1, 2026
  12. v0.7.0Oct 1, 2026
  13. v0.6.0Sep 30, 2026
  14. v0.5.2Sep 30, 2026
  15. v0.5.1Sep 29, 2026
  16. v0.5.0Sep 28, 2026
  17. v0.3.0Sep 23, 2026
  18. v0.2.0Sep 21, 2026
  19. v0.1.0Sep 18, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分