Vessel Tracking
NPM · @PIPEWORX/MCP-VESSEL-TRACKING · 2 COMPONENTS
Vessel Tracking — live worldwide ship positions from AIS.
Available components
Last scanned (10 hours ago)
Scores higher than 58% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-vessel-tracking). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 985 tokens (~328/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-vessel-tracking@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-vessel-tracking |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-vessel-tracking/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560944726 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6eebdc41cb802ad272724e13adf67915893181ef651b9c4636275d5aa4782a165bcf55d38acd648be8c829f93d8519bf454a83bce9acf374de52adf92 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ais_coverage_check ~164
Does live AIS tracking actually work at this location? Listens at a point and reports whether any community receiver covers it, so you can tell the difference between "no ships here" and "no receivers here" before trusting a zero. Use this whenever a vessel search comes back empty, and always before treating an empty result as evidence that shipping has stopped.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | aisstream.io API key (free at aisstream.io) |
| latitude | number | yes | Latitude to test |
| longitude | number | yes | Longitude to test |
| radius_km | number | – | Radius to test around the point in km (default 150) |
| window_seconds | number | – | How long to listen, 3-25 seconds (default 15) |
No output schema declared.
No examples provided.
live_ship_position ~351
Where is a specific ship right now — live AIS position for one or more vessels by MMSI number. Returns position, speed, course, navigational status and destination as currently broadcast. BEST EFFORT BY NATURE: this listens for a live broadcast rather than reading a stored position, and many vessels transmit less than once a minute, so a single call frequently hears nothing even for a ship that is definitely sailing. Measured behaviour, not a caveat for form. Improve the odds with a longer window_seconds, or use live_ships_in_area if you know roughly where the ship is. For a guaranteed last-known position rather than a live catch, use vesselfinder_vessel (paid key). COVERAGE IS PARTIAL AND TERRESTRIAL — there is no receiver coverage in the Persian Gulf, Strait of Hormuz, Gulf of Oman or Red Sea, so this tool cannot answer questions about those waters (use chokepoint_status for Hormuz/Suez/Bab el-Mandeb transit counts instead). Counts are vessels heard during a listening window of a few seconds, not a complete count of vessels present.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | aisstream.io API key (free at aisstream.io) |
| mmsi | array | yes | One or more 9-digit MMSI numbers, e.g. ["219034351"] |
| window_seconds | number | – | How long to listen, 3-40 seconds (default 30). Hit rate scales almost linearly with this: many vessels transmit less than once a minute, so a 10-second window will usually miss and a 40-second one of… |
No output schema declared.
No examples provided.
live_ships_in_area ~415
Live ship positions right now in a geographic area, from AIS radio broadcasts — what vessels are sailing near a port, coastline, strait or set of coordinates at this moment. Returns each vessel heard with its position, speed, course, navigational status, type, destination and IMO where broadcast, plus a breakdown by vessel type (cargo, tanker, passenger, fishing, tug). Give either a centre point (latitude + longitude + radius_km) or a bounding box. COVERAGE IS PARTIAL AND TERRESTRIAL — there is no receiver coverage in the Persian Gulf, Strait of Hormuz, Gulf of Oman or Red Sea, so this tool cannot answer questions about those waters (use chokepoint_status for Hormuz/Suez/Bab el-Mandeb transit counts instead). Counts are vessels heard during a listening window of a few seconds, not a complete count of vessels present.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | aisstream.io API key (free at aisstream.io) |
| east | number | – | Bounding box eastern longitude |
| latitude | number | – | Centre latitude, e.g. 43.3 for Marseille |
| limit | number | – | Maximum vessels to return (default 50, max 300) |
| longitude | number | – | Centre longitude, e.g. 5.4 for Marseille |
| north | number | – | Bounding box northern latitude |
| radius_km | number | – | Radius around the centre point in km (default 50, max 500) |
| ship_type | string | – | Optional filter on decoded type, e.g. "tanker", "cargo", "passenger", "fishing", "tug" |
| south | number | – | Bounding box southern latitude (alternative to centre+radius) |
| west | number | – | Bounding box western longitude |
| window_seconds | number | – | How long to listen, 3-25 seconds (default 12). Longer windows hear more vessels, especially anchored ones which only transmit every ~3 minutes. |
No output schema declared.
No examples provided.
How do I install the Vessel Tracking MCP server?
Vessel Tracking runs locally as an npm package, launched with npx -y @pipeworx/mcp-vessel-tracking. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-vessel-tracking
claude mcp add pipeworx-io-vessel-tracking -- npx -y @pipeworx/mcp-vessel-tracking
What is the Vessel Tracking MCP server?
Vessel Tracking is an MCP server listed in the public MCP registry as io.github.pipeworx-io/vessel-tracking. Vessel Tracking, live worldwide ship positions from AIS. This page covers its npm package (@pipeworx/mcp-vessel-tracking).
Is the Vessel Tracking MCP server safe to use?
Vessel Tracking scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Vessel Tracking MCP server expose?
Vessel Tracking exposes 3 tools: live_ships_in_area, live_ship_position, ais_coverage_check. Their descriptions and schemas cost roughly 930 tokens of context every time the server is loaded.
Is the Vessel Tracking MCP server still maintained?
Vessel Tracking is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Vessel Tracking MCP server under?
Vessel Tracking declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Vessel Tracking MCP server?
VerifyMCP ran 15 checks on Vessel Tracking, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Vessel Tracking: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.