Security & Testing

arcnautical.com

Screens vessels by IMO number against global sanctions lists and port-state-control history, returning sanctions matches, ownership-opacity scores, vetting grades, and retained audit records.

1 endpoint7 known toolsFirst detected September 13, 2026Last detected September 13, 2026

ENDPOINT 1

https://mcp.arcnautical.com/mcp

No auth detected

MCP server metadata

Name: arcnautical
Version: 0.2.0

Capabilities

tools.listChangedresourcesprompts

Server instructions

ArcNautical screens commercial vessels for sanctions and risk. Identify a ship by its seven-digit IMO number (never by name alone: names repeat and change). Use check_vessel for a quick verdict with no key; use screen_vessel for the full evidence record when an API key is configured. Sanctions status semantics: RED = confirmed match on the vessel identifier, AMBER = possible match needing review, GREEN = no match against the sources reached, INCOMPLETE = a core source could not be read, which must never be presented as clear. Always quote the status, the checkedAt/screened_at time, and say that designations change daily.

Known tools 7

check_vessel

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.

Inferred read-only

find_port

Resolve a port name, country or partial UN/LOCODE to the LOCODEs the routing engine knows.

Inferred read-only

screen_vessel

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.

Inferred read-only

screen_vessels

Batch-screen a list of IMO numbers and wait for the results (up to two minutes).

Inferred read-only

get_screening

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

Inferred read-only

score_voyage

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.

Inferred read-only

get_usage

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.arcnautical]
url = "https://mcp.arcnautical.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "arcnautical": {
      "type": "http",
      "url": "https://mcp.arcnautical.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: arcnautical
Remote MCP URL: https://mcp.arcnautical.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "arcnautical": {
      "url": "https://mcp.arcnautical.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "arcnautical": {
      "type": "http",
      "url": "https://mcp.arcnautical.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "arcnautical",
  "transport": "streamable-http",
  "url": "https://mcp.arcnautical.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.