Vessel Tracking — live worldwide ship positions from AIS.
MCPpedia last refreshed this data
io.github.pipeworx-io/vessel-tracking is an MCP server that vessel Tracking — live worldwide ship positions from AIS. Its tool list has not been published yet over http, requires no API key, and scores 70/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vessel-tracking": {
"url": "https://gateway.pipeworx.io/vessel-tracking/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Live worldwide ship positions from AIS radio broadcasts. Platform key (aisstream.io), BYO accepted.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics
MCP Server for GCP environment for interacting with various Observability APIs.
MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.
Trending hip-hop artist momentum scores across four cultural dimensions.
MCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/vessel-tracking and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Live worldwide ship positions from AIS radio broadcasts. Platform key (aisstream.io), BYO accepted.
Part of Pipeworx — an MCP gateway connecting AI agents to 1394+ live data sources.
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.live_ship_position(...) — live position for specific vessels by MMSI.ais_coverage_check(...) — whether any receiver actually covers a location, so a zero can be read correctly.Platform key (PLATFORM_AISSTREAM_KEY), or BYO via _apiKey. Free, instant signup at https://aisstream.io.
aisstream is a community network of terrestrial receivers, so coverage follows where volunteers run hardware. Verified 2026-07-27 with a 60-second subscription:
| Region | Vessels heard |
|---|---|
| Mediterranean | 221 |
| English Channel | 50 (30s) |
| Strait of Malacca | 24 (30s) |
| Persian Gulf / Strait of Hormuz | 0 |
| Gulf of Oman | 0 |
| Red Sea / Bab el-Mandeb | 0 |
There 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.
The 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.
AIS 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.
wss://stream.aisstream.io/v0/streamAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"vessel-tracking": {
"url": "https://gateway.pipeworx.io/vessel-tracking/mcp"
}
}
}
Or connect to the full Pipeworx gateway for access to all 1394+ data sources:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Instead of calling tools directly, you can ask questions in plain English:
ask_pipeworx({ question: "your question about Vessel Tracking data" })
The gateway picks the right tool and fills the arguments automatically.
MIT