aiscast, the Open Waters AIS network: aisstream.io-compatible streams from open
aiscast, the Open Waters AIS network: aisstream.io-compatible streams from open feeds and volunteer receivers
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://ais.openwaters.io/mcp |
|---|---|
| Source | https://github.com/openwatersio/aiscast |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-11-10 22:00:11 |
| Last checked | 2026-11-17 21:54:50 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 416 / 593 ms |
| Last successful check | 2026-11-17 21:54:50 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
find_vessels_in_area— Vessels currently inside a latitude/longitude bounding box, newest report first, with optional kind and ship-type filters. Anonymous calls mfind_vessels_near— Vessels within a radius (default 10 NM, maximum 50) of a point or of another vessel's last known position, nearest first, each with distanceget_coverage— Where Open Waters AIS is hearing AIS right now: sources with their current delay, stations, freshness, and vessel counts. A bounding box addget_vessel_track— The positions heard from one vessel over a time range, oldest first, with speed, course, and navigational status. Positions implying an impoget_vessels— Last known position and particulars of specific vessels by MMSI (Maritime Mobile Service Identity), or by IMO number with a feeder or partnesearch_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
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:54:50 | ✓ | ✓ | 511 ms | 90 | active |
| 2026-11-17 21:39:37 | ✓ | ✓ | 304 ms | 90 | active |
| 2026-11-17 21:24:19 | ✓ | ✓ | 458 ms | 90 | active |
| 2026-11-17 21:09:11 | ✓ | ✓ | 437 ms | 90 | active |
| 2026-11-17 20:54:02 | ✓ | ✓ | 585 ms | 90 | active |
| 2026-11-17 20:39:00 | ✓ | ✓ | 407 ms | 90 | active |
| 2026-11-17 20:23:56 | ✓ | ✓ | 443 ms | 90 | active |
| 2026-11-17 20:08:47 | ✓ | ✓ | 329 ms | 90 | active |
| 2026-11-17 19:52:59 | ✓ | ✓ | 321 ms | 90 | active |
| 2026-11-17 19:37:55 | ✓ | ✓ | 496 ms | 90 | active |
| 2026-11-17 19:22:32 | ✓ | ✓ | 315 ms | 90 | active |
| 2026-11-17 19:07:22 | ✓ | ✓ | 289 ms | 94 | active |
| 2026-11-17 18:52:05 | ✓ | ✓ | 428 ms | 90 | active |
| 2026-11-17 18:36:59 | ✓ | ✓ | 391 ms | 90 | active |
| 2026-11-17 18:21:55 | ✓ | ✓ | 433 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://ais.openwaters.io/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/ais-openwaters-io-mcp # JSON