# com.arcnautical/mcp (npm · @arcnautical/mcp)

Screen any vessel by IMO for sanctions, ownership opacity and vetting grade. Keyless check included.

- Trust score: 74/100 (medium)
- Change this week: +29
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `mcp.arcnautical.com`: 68/100, [markdown](https://verifymcp.io/servers/com-arcnautical-mcp/mcp.md), [page](https://verifymcp.io/servers/com-arcnautical-mcp/mcp)
- npm · `@arcnautical/mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-arcnautical-mcp/arcnautical-mcp.md), [page](https://verifymcp.io/servers/com-arcnautical-mcp/arcnautical-mcp)

## Channel facts

- Registry: `npm`
- Package: `@arcnautical/mcp`
- 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-09-25.

- **Supply Chain Security**: 98/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.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 963 tokens (~137/item across 7 items; 7 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 com.arcnautical/mcp server?

com.arcnautical/mcp runs locally as an npm package, launched with npx -y @arcnautical/mcp. 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 com-arcnautical-mcp -- npx -y @arcnautical/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-arcnautical-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@arcnautical/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-arcnautical-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@arcnautical/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-arcnautical-mcp -- npx -y @arcnautical/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-arcnautical-mcp --command npx --arg -y --arg @arcnautical/mcp
```

### Hermes

```yaml
mcp_servers:
  com-arcnautical-mcp:
    command: "npx"
    args: ["-y", "@arcnautical/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-arcnautical-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@arcnautical/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-arcnautical-mcp -t stdio -c npx -a -y @arcnautical/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-arcnautical-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@arcnautical/mcp"
      ]
    }
  }
}
```

## 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-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 74, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-23 (score 58, −12)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Tool coverage: 71% → 100%
- [functional improvement] Stability: unverified → 0.17
- [functional] First check of Tool coverage: 100
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-09-19 (score 70, +25)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-09-18 (score 45)

First indexed and scored.

## MCP tools (7)

### `check_vessel` (~111 tokens)

Check a vessel (no key)

Screen one vessel by IMO number against OFAC SDN, EU, UN, UK OFSI and OpenSanctions, with an ownership-opacity score and an A–E vetting grade from port-state-control history. Works with no API key. Rate-limited to 100 requests per hour per IP. Returns the VERDICT SUMMARY only; for every sanctions match with its source list and confidence class use screen_vessel (needs a key).

Input parameters:

- `imo` (string, required): Seven-digit IMO number of the vessel

Output parameters:

- `assessed` (boolean): false means ownership and vetting are defaults, not findings
- `checkedAt` (string): ISO-8601 time the sources were read; designations change daily
- `fullReport` (string): Human-readable report URL for this hull
- `imo` (string): The seven-digit IMO number screened
- `ownership` (object)
- `rate_limit` (object): Keyless allowance for the caller's address
- `sanctions` (object)
- `vetting` (object)

### `find_port` (~105 tokens)

Find a port / UN/LOCODE (no key)

Resolve a port name, country or partial UN/LOCODE to the LOCODEs the routing engine knows. Routes are addressed by LOCODE, so call this before score_voyage rather than guessing a code. Works with no API key.

Input parameters:

- `limit` (integer): Maximum matches to return (default 5)
- `query` (string, required): Port name, country, or LOCODE fragment, e.g. "rotterdam", "NLRTM", "Piraeus"

Output parameters:

- `ports` (array): Best matches first

### `screen_vessel` (~191 tokens)

Screen a vessel (full record, API key)

The authenticated screening record for one vessel: every sanctions match with its source list, programme and confidence class, ownership opacity, the graded vetting factors, per-source freshness, and a retained record id. Needs ARCNAUTICAL_API_KEY. Metered: 5,000 live screenings a month are included with a self-serve key. The same vessel asked again on the same day replays the stored record free. If the result is INCOMPLETE for identity, call again with vessel_name.

Input parameters:

- `customer_reference` (string): Your own reference (order id, voyage id); echoed on the record
- `imo` (string, required): Seven-digit IMO number of the vessel
- `include_vetting` (boolean): false skips the vetting grade for a faster sanctions-only screen
- `vessel_name` (string): Only when a previous screen was INCOMPLETE for identity; a name you can confirm

Output parameters:

- `id` (string): Screening record id, retained ten years
- `imo` (string)
- `ownership` (object)
- `sanctions` (object)
- `screened_at` (string): ISO-8601 time the sources were read
- `vessel_name` (string|null)
- `vetting` (object)

### `screen_vessels` (~96 tokens)

Screen up to 50 vessels (API key)

Batch-screen a list of IMO numbers and wait for the results (up to two minutes). Returns one verdict per hull plus the batch status. Needs ARCNAUTICAL_API_KEY. Each hull spends one screening unit unless it was already screened today.

Input parameters:

- `imos` (array, required): Up to 50 seven-digit IMO numbers
- `include_vetting` (boolean): false skips the vetting grade for a faster sanctions-only screen

Output parameters:

- `batch` (object): The batch as last read
- `items` (array): One row per hull

### `get_screening` (~52 tokens)

Retrieve a screening record (API key)

Fetch a stored screening record by id — the audit copy, retained ten years. Needs ARCNAUTICAL_API_KEY.

Input parameters:

- `id` (string, required): Screening id returned by screen_vessel or in a batch item

Output parameters:

- `id` (string): Screening record id, retained ten years
- `imo` (string)
- `ownership` (object)
- `sanctions` (object)
- `screened_at` (string): ISO-8601 time the sources were read
- `vessel_name` (string|null)
- `vetting` (object)

### `score_voyage` (~243 tokens)

Score a voyage route (API key)

Route risk between two ports (UN/LOCODEs): a 0–100 score, risk level, the signals driving it (war-risk areas, piracy, chokepoints, weather, sanctions exposure of transited EEZs), confidence and any missing sources. Resolve port names with find_port first. Needs ARCNAUTICAL_API_KEY; 10,000 assessments a month are included with a self-serve key.

Input parameters:

- `customer_reference` (string): Your own reference (voyage id, fixture); echoed on the assessment
- `destination` (string, required): Destination UN/LOCODE, e.g. CNSHA
- `dwt_tonnes` (number): Deadweight in tonnes; used for chokepoint and draught constraints
- `load_condition` (string): laden or ballast; affects exposure on the transit
- `origin` (string, required): Origin UN/LOCODE, e.g. NLRTM
- `speed_knots` (number): Planned service speed, 8-25 knots; sets transit time through each risk area
- `vessel_type` (string): Vessel class; changes which threat signals weigh most (default: general)

Output parameters:

- `confidence` (number): 0-1
- `id` (string): Assessment id
- `missing_sources` (array): Signals that could not be read for this assessment
- `risk_level` (string): low | moderate | elevated | high | severe
- `route` (object)
- `score` (number): 0-100, higher is riskier
- `signals`

### `get_usage` (~29 tokens)

Usage and quota (API key)

Live and test usage, remaining allowance, reset time, batch limits and monitor capacity for the configured key.

Output parameters:

- `assessments` (object): Allowance, used, remaining and reset per environment
- `environment` (string): live | test
- `limits` (object)
- `screenings` (object)

## Diagnostics

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

## Score history

- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 58
- 2026-09-22: 70
- 2026-09-21: 70
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 45

## Common questions

### What is the com.arcnautical/mcp server?

com.arcnautical/mcp is listed in the public MCP registry as com.arcnautical/mcp. Screen any vessel by IMO for sanctions, ownership opacity and vetting grade. Keyless check included. This page covers its npm package (@arcnautical/mcp).

### Is the com.arcnautical/mcp server safe to use?

com.arcnautical/mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 com.arcnautical/mcp server expose?

com.arcnautical/mcp exposes 7 tools: check_vessel, find_port, screen_vessel, screen_vessels, get_screening, and 2 more. Their descriptions and schemas cost roughly 827 tokens of context every time the server is loaded.

### Is the com.arcnautical/mcp server still maintained?

com.arcnautical/mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 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 com.arcnautical/mcp server under?

com.arcnautical/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@arcnautical/mcp
- Socket report: https://socket.dev/npm/package/@arcnautical/mcp
- Repository: https://github.com/arcnautical/arcnautical-mcp
- Website: https://arcnautical.com/developers/
- Changelog RSS feed: https://verifymcp.io/servers/com-arcnautical-mcp/arcnautical-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-arcnautical-mcp/arcnautical-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-arcnautical-mcp/arcnautical-mcp