Digitraffic Ais
NPM · @PIPEWORX/MCP-DIGITRAFFIC-AIS · 2 COMPONENTS
Digitraffic AIS MCP — live vessel positions in Finnish and Baltic Sea waters.
Available components
Last scanned (7 hours ago)
Scores higher than 69% 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-digitraffic-ais). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 988 tokens (~329/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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 +1
- 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-digitraffic-ais@0.2.1
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-digitraffic-ais |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-digitraffic-ais/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617516441 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ed326ccb5cbc99f2e8a688a434f582cc0ce823e4517e96b9617bc7022ec116d8cf5dc78fc1bc0cd7ad51b1807822c488cd175cec5026dea7eee553f43 |
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_area_count ~382
Count how many ships are in an area right now, broken down by ship-type category and by whether they are moving or stationary. Answers "how many vessels are in this area", "how many tankers are in the Gulf of Finland", "ship traffic count in a bounding box", "how many vessels are anchored off Helsinki". Give EITHER a circle (latitude, longitude, radius_km) OR a bounding box (min_lat, max_lat, min_lon, max_lon). Returns total, by_category counts (cargo, tanker, passenger, fishing, other), moving versus stationary using a 0.5-knot threshold, and the data timestamp. COVERAGE IS REGIONAL: Fintraffic AIS receivers over Finland and the surrounding Baltic Sea; an area elsewhere in the world counts zero. Example: min_lat 59.3, max_lat 60.5, min_lon 22.0, max_lon 28.0 for the Gulf of Finland; or latitude 60.15, longitude 24.95, radius_km 50 for Helsinki.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | – | Circle mode: centre latitude in decimal degrees. |
| longitude | number | – | Circle mode: centre longitude in decimal degrees. |
| max_lat | number | – | Bounding-box mode: northern latitude edge. |
| max_lon | number | – | Bounding-box mode: eastern longitude edge. |
| min_lat | number | – | Bounding-box mode: southern latitude edge. |
| min_lon | number | – | Bounding-box mode: western longitude edge. |
| radius_km | number | – | Circle mode: radius in kilometres. Default 25, maximum 100. |
| vessel_type | string | – | Optional ship-type filter applied before counting. One of: cargo, tanker, passenger, fishing, tug, pilot, sar, military, sailing, pleasure, high-speed, service, other. |
No output schema declared.
No examples provided.
ais_vessel ~183
Look up one specific ship by its MMSI number and get its registered details plus its latest AIS position. Returns name, call sign, IMO number, ship type, length and beam, draught, reported destination and ETA, then the live position: lat/lon, speed in knots, course, heading, navigational status, and when the report was received. Use for "where is MMSI 230052800", "track this vessel", "what ship is this MMSI". COVERAGE IS REGIONAL: the ship must have been heard by a Fintraffic receiver in Finland or the surrounding Baltic Sea. Get an MMSI from ais_vessels_near first. Example: mmsi 230052800.
| Name | Type | Req | Description |
|---|---|---|---|
| mmsi | number | yes | Maritime Mobile Service Identity, a 9-digit vessel number, e.g. 230052800. |
No output schema declared.
No examples provided.
ais_vessels_near ~365
Live vessel positions near a point: which ships are in the water around a location right now, from AIS vessel tracking. Returns per ship the MMSI, vessel name, ship type (cargo, tanker, passenger ferry, fishing, tug, sailing, pleasure craft, military), speed in knots, course, navigational status (under way, at anchor, moored, fishing), lat/lon, distance from the centre, and how fresh the report is. Use for "what ships are near Helsinki", "vessel traffic outside Turku", "is anything anchored off this port", "boats in the Gulf of Finland". COVERAGE IS REGIONAL: Fintraffic AIS receivers cover Finland and the surrounding Baltic Sea (Gulf of Finland, Gulf of Bothnia, Archipelago Sea, Åland, fringe reception toward Estonia and Sweden). Points elsewhere in the world return nothing. Example: latitude 60.15, longitude 24.95, radius_km 50 for Helsinki; add vessel_type "tanker" to see only tankers.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Centre latitude in decimal degrees, e.g. 60.15 for Helsinki. |
| limit | number | – | Maximum vessels to return, nearest first. Default 50, maximum 200. |
| longitude | number | yes | Centre longitude in decimal degrees, e.g. 24.95 for Helsinki. |
| radius_km | number | – | Search radius in kilometres. Default 25, maximum 100. |
| vessel_type | string | – | Optional ship-type filter. One of: cargo, tanker, passenger, ferry, cruise, fishing, tug, towing, pilot, sar, military, sailing, pleasure, yacht, law enforcement, dredging, high-speed, service, other. |
No output schema declared.
No examples provided.
How do I install the Digitraffic Ais MCP server?
Digitraffic Ais runs locally as an npm package, launched with npx -y @pipeworx/mcp-digitraffic-ais. 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-digitraffic-ais
claude mcp add pipeworx-io-digitraffic-ais -- npx -y @pipeworx/mcp-digitraffic-ais
What is the Digitraffic Ais MCP server?
Digitraffic Ais is an MCP server listed in the public MCP registry as io.github.pipeworx-io/digitraffic-ais. Digitraffic AIS MCP, live vessel positions in Finnish and Baltic Sea waters. This page covers its npm package (@pipeworx/mcp-digitraffic-ais).
Is the Digitraffic Ais MCP server safe to use?
Digitraffic Ais scores 81 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 Digitraffic Ais MCP server expose?
Digitraffic Ais exposes 3 tools: ais_vessels_near, ais_area_count, ais_vessel. Their descriptions and schemas cost roughly 930 tokens of context every time the server is loaded.
Is the Digitraffic Ais MCP server still maintained?
Digitraffic Ais 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 Digitraffic Ais MCP server under?
Digitraffic Ais declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.