{
  "markdown": "# @pipeworx/vessel-tracking\n\nLive worldwide ship positions from AIS radio broadcasts. Platform key (aisstream.io), BYO accepted.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `live_ships_in_area(...)` — vessels broadcasting right now in a bounding box or around a point, with position, speed, course, navigational status, type, destination and IMO, plus a breakdown by vessel type.\n- `live_ship_position(...)` — live position for specific vessels by MMSI.\n- `ais_coverage_check(...)` — whether any receiver actually covers a location, so a zero can be read correctly.\n\n## Auth\n\nPlatform key (`PLATFORM_AISSTREAM_KEY`), or BYO via `_apiKey`. Free, instant signup at https://aisstream.io.\n\n## Coverage — read this before trusting a zero\n\naisstream is a community network of **terrestrial** receivers, so coverage follows where volunteers run hardware. Verified 2026-07-27 with a 60-second subscription:\n\n| Region | Vessels heard |\n|---|---|\n| Mediterranean | 221 |\n| English Channel | 50 (30s) |\n| Strait of Malacca | 24 (30s) |\n| **Persian Gulf / Strait of Hormuz** | **0** |\n| **Gulf of Oman** | **0** |\n| **Red Sea / Bab el-Mandeb** | **0** |\n\nThere is **no coverage of the Gulf or Red Sea**. Satellite AIS — the paid product from Spire/ORBCOMM — is what covers open ocean and unreceivered coasts, and this is not that. Asking about Hormuz returns `coverage: \"none\"` with a redirect to `chokepoint_status`, never a bare `0`.\n\nThe count field is named `vessels_observed`, not `vessel_count`, because it measures what was heard in a listening window rather than what is present. Every zero carries a `coverage` verdict of `confirmed`, `none` or `unconfirmed`.\n\n### Sampling caveat\n\nAIS transmit intervals depend on motion: a vessel underway broadcasts every 2-10 seconds, one at anchor roughly every 3 minutes. Short windows therefore under-count stationary ships. `live_ship_position` is **best effort by nature** — a 35s window found 1 of 8 vessels confirmed transmitting moments earlier — so widen `window_seconds` (max 40; beyond that callers time out) or use `vesselfinder_vessel` for a stored last-known position.\n\n## Data sources\n\n- Stream: `wss://stream.aisstream.io/v0/stream`\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"vessel-tracking\": {\n      \"url\": \"https://gateway.pipeworx.io/vessel-tracking/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/vessel-tracking/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Vessel Tracking data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4320,
  "sha": "86c9af706ef5fff16cc7fd3e20fcf1025586a997adabef627f90fafcd3fecf66",
  "repo_slug": "pipeworx-io/mcp-vessel-tracking",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_vessel_tracking_82edfb22/readme"
}