# Digitraffic Ais (npm · @pipeworx/mcp-digitraffic-ais)

Digitraffic AIS MCP — live vessel positions in Finnish and Baltic Sea waters.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/digitraffic-ais-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/digitraffic-ais-mcp)
- npm · `@pipeworx/mcp-digitraffic-ais`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/pipeworx-mcp-digitraffic-ais.md), [page](https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/pipeworx-mcp-digitraffic-ais)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-digitraffic-ais`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-digitraffic-ais).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-digitraffic-ais -- npx -y @pipeworx/mcp-digitraffic-ais
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-digitraffic-ais": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-digitraffic-ais"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-digitraffic-ais": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-digitraffic-ais"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-digitraffic-ais -- npx -y @pipeworx/mcp-digitraffic-ais
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-digitraffic-ais": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-digitraffic-ais"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-digitraffic-ais --command npx --arg -y --arg @pipeworx/mcp-digitraffic-ais
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-digitraffic-ais:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-digitraffic-ais"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-digitraffic-ais": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-digitraffic-ais"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-digitraffic-ais -t stdio -c npx -a -y @pipeworx/mcp-digitraffic-ais
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-digitraffic-ais": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-digitraffic-ais"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 81, +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.

### 2026-11-01 (score 80, +1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.07 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `ais_vessels_near` (~365 tokens)

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.

Input parameters:

- `latitude` (number, required): 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, required): 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.

### `ais_area_count` (~382 tokens)

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.

Input parameters:

- `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.

### `ais_vessel` (~183 tokens)

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.

Input parameters:

- `mmsi` (number, required): Maritime Mobile Service Identity, a 9-digit vessel number, e.g. 230052800.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/pipeworx-mcp-digitraffic-ais#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### 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.

### What did VerifyMCP test on the Digitraffic Ais MCP server?

VerifyMCP ran 16 checks on Digitraffic Ais, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-digitraffic-ais
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-digitraffic-ais
- Repository: https://github.com/pipeworx-io/mcp-digitraffic-ais
- Website: https://pipeworx.io/packs/digitraffic-ais
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/pipeworx-mcp-digitraffic-ais.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/pipeworx-mcp-digitraffic-ais/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/pipeworx-mcp-digitraffic-ais.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-digitraffic-ais/pipeworx-mcp-digitraffic-ais