# arcnautical.com MCP server (slim)

> arcnautical.com MCP server, an MCP server by arcnautical.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Screen any vessel by IMO for sanctions, ownership opacity and vetting grade. Keyless check included.

- Full: https://www.anchorterminal.com/tools/arcnautical-mcp.md (~850 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/tools/arcnautical-mcp.json · canonical https://www.anchorterminal.com/tools/arcnautical-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-04

# arcnautical.com MCP server

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by arcnautical.com (https://arcnautical.com/developers/)
- Listed because: It's published in the registry under arcnautical.com, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: Screen any vessel by IMO for sanctions, ownership opacity and vetting grade. Keyless check included.

## Facts

- MCP registry: `com.arcnautical/mcp` 0.2.1
- Endpoint: https://mcp.arcnautical.com/mcp (streamable HTTP)
- Package: npm `@arcnautical/mcp` (stdio)
- Source: https://github.com/arcnautical/arcnautical-mcp
- Website: https://arcnautical.com/developers/
- npm downloads a week: 239
- GitHub stars: 0
- Registry entry updated: 2026-09-23

## Tools

- Tools it lists (7, about 3,005 tokens of context, `tools/list` without credentials over MCP 2025-11-25, checked 2026-10-04 22:22 UTC):
  - `check_vessel` (read-only): 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…
  - `find_port` (read-only): 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…
  - `screen_vessel` (writes): The authenticated screening record for one vessel: every sanctions match with its source list, programme and confidence class, ownership opacity, the graded…
  - `screen_vessels` (writes): 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.…
  - `get_screening` (read-only): Fetch a stored screening record by id — the audit copy, retained ten years. Needs ARCNAUTICAL_API_KEY.
  - `score_voyage` (writes): 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…
  - `get_usage` (read-only): Live and test usage, remaining allowance, reset time, batch limits and monitor capacity for the configured key.
- How its tools read to an agent (0 errors, 0 warnings, 0 notes, about 3,005 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):

- JSON: https://www.anchorterminal.com/api/v1/tools/arcnautical-mcp.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming