ArcNautical MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to ArcNautical vessel sanctions and ownership screening: Do vetting grades retain current attributable sources and remain distinct from a compliance certification?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Vessel sanctions, ownership-opacity and voyage-risk screening by IMO.

What we know

Maritime compliance MCP with keyless vessel checks/port resolution plus keyed full screening, batch screening, record retrieval, voyage scoring and usage.

Maintenance / activity evidence

@arcnautical/mcp 0.2.1 published 2026-09-23T15:50:07.037Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read/compliance screening plus provider-side retained screening records. Writes: Create retained screening records; Potential monitoring/provider-side screening resources.
Optional API key.
Sensitive access: Vessel identity, Sanctions/ownership/vetting data, API key, Route/port context

Compliance output can be incomplete or stale; never equate a green result with full clearance unless coverage and timestamp support it.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do vetting grades retain current attributable sources and remain distinct from a compliance certification?

The bounded review of the publisher's documented ArcNautical vessel sanctions and ownership screening and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Compliance output can be incomplete or stale; never equate a green result with full clearance unless coverage and timestamp support it.
Read/compliance screening plus provider-side retained screening records.
Optional API key.
Screening evidence and vessel/route data are processed by ArcNautical; stored screening records have long retention per provider docs.
Reviewed write actions: Create retained screening records; Potential monitoring/provider-side screening resources
Sensitive access: Vessel identity, Sanctions/ownership/vetting data, API key, Route/port context
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public repository identity
Keyless checks can miss renamed-hull history.
GREEN is not clearance if coverage is incomplete; INCOMPLETE must not be presented as clear.
Designations change daily, so timestamps matter.
Keyed calls have allowances/rate limits and create retained screening records.

Original activity observations

@arcnautical/mcp 0.2.1 published 2026-09-23T15:50:07.037Z

Technical identity

npm/@arcnautical/mcp

Exact implementation source: https://www.npmjs.com/package/@arcnautical/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@arcnautical/mcp
Service endpoint: https://mcp.arcnautical.com/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@arcnautical/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
arcnautical.com/developers/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
arcnautical.com/developers/reference/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
arcnautical.com/llms.txt
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher supports hosted https://mcp.arcnautical.com/mcp, OR local stdio npx -y @arcnautical/mcp. Hosted free check_vessel/find_port calls require no API key; keyed tools need provider key in request Authorization.
client registration · Claude Code only · Publisher instructions
claude mcp add --transport http arcnautical https://mcp.arcnautical.com/mcp
Configure / authenticate
MCP100 setup guide
For basic vessel checks use public hosted MCP without key; keyed tools need Authorization: Bearer or stdio ARCNAUTICAL_API_KEY. Endpoint `/health` is HTTP health not auth proof.
Check connection
Suggested check
Use keyless `check_vessel` against public IMO; `GET /health` only proves reachability.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `arcnautical`, remove the client entry with `claude mcp remove arcnautical`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove arcnautical

Official Documentation & Sources

https://www.npmjs.com/package/@arcnautical/mcp ↗

What it does

Maritime compliance MCP with keyless vessel checks/port resolution plus keyed full screening, batch screening, record retrieval, voyage scoring and usage.

Capability: Security & Testing
Resource type: MCP Server
Industry: Logistics & Supply Chain, Legal & Compliance
Best fit: Vessel sanctions, ownership-opacity and voyage-risk screening by IMO.

Representative uses

Check sanctions across major lists
Resolve ports
Retrieve matches/source freshness
Batch screen IMOs
Score routes
Inspect ownership/vetting grade

Limitations

Keyless checks can miss renamed-hull history.
GREEN is not clearance if coverage is incomplete; INCOMPLETE must not be presented as clear.
Designations change daily, so timestamps matter.
Keyed calls have allowances/rate limits and create retained screening records.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Optional API key.
Permissions: Read/compliance screening plus provider-side retained screening records.
Data handling: Screening evidence and vessel/route data are processed by ArcNautical; stored screening records have long retention per provider docs.
Cost: freemium
Risk and cautions: Compliance output can be incomplete or stale; never equate a green result with full clearance unless coverage and timestamp support it.

Access scope and cautions

Write actions: Create retained screening records Potential monitoring/provider-side screening resources
Sensitive access: Vessel identity Sanctions/ownership/vetting data API key Route/port context
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Check sanctions across major lists; Resolve ports; Retrieve matches/source freshness; Batch screen IMOs; Score routes; Inspect ownership/vetting grade.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @arcnautical/mcp. Recorded endpoint: https://mcp.arcnautical.com/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: ARCNAUTICAL_API_KEY (keyed tools); ARCNAUTICAL_BASE_URL (optional); PORT/HOST/MCP_TRUST_PROXY (self-hosted HTTP). No configuration values are supplied here. Prerequisites: Node.js 18+ local; API key for full/batch/voyage tools. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Keyless basic tools; full screening uses API key/bearer header. A demo or keyless description is not independently verified read-only authority. Check the documented tool permissions rather than inferring authority from that label.

Can it modify data or perform write operations?

Documented write actions include: Create retained screening records; Potential monitoring/provider-side screening resources. Recorded permission boundary: Read/compliance screening plus provider-side retained screening records.

What data-handling boundary should I consider?

Screening evidence and vessel/route data are processed by ArcNautical; stored screening records have long retention per provider docs. Recorded sensitive-access context: Vessel identity; Sanctions/ownership/vetting data; API key; Route/port context.

What limitations and risks should I check before use?

Compliance output can be incomplete or stale; never equate a green result with full clearance unless coverage and timestamp support it. Keyless checks can miss renamed-hull history. GREEN is not clearance if coverage is incomplete; INCOMPLETE must not be presented as clear. Designations change daily, so timestamps matter. Keyed calls have allowances/rate limits and create retained screening records. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

ArcNautical is listed as First-party MCP in MCP100’s current evidence.