com.arcnautical/mcp
REMOTE · MCP.ARCNAUTICAL.COM · 2 COMPONENTS · SCANNED SEP 25
Screen any vessel by IMO for sanctions, ownership opacity and vetting grade. Keyless check included.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.arcnautical/mcp server?
com.arcnautical/mcp is a hosted endpoint at https://mcp.arcnautical.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.arcnautical.com
claude mcp add --transport http com-arcnautical-mcp 'https://mcp.arcnautical.com/mcp'
{
"mcpServers": {
"com-arcnautical-mcp": {
"url": "https://mcp.arcnautical.com/mcp"
}
}
} {
"servers": {
"com-arcnautical-mcp": {
"type": "http",
"url": "https://mcp.arcnautical.com/mcp"
}
}
} [mcp_servers.com-arcnautical-mcp] url = "https://mcp.arcnautical.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-arcnautical-mcp": {
"type": "remote",
"url": "https://mcp.arcnautical.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-arcnautical-mcp --url 'https://mcp.arcnautical.com/mcp' --transport streamable-http
mcp_servers:
com-arcnautical-mcp:
url: "https://mcp.arcnautical.com/mcp" {
"McpServers": {
"com-arcnautical-mcp": {
"Transport": "http",
"Url": "https://mcp.arcnautical.com/mcp"
}
}
} assistant mcp add com-arcnautical-mcp -t streamable-http -u 'https://mcp.arcnautical.com/mcp'
{
"mcpServers": {
"com-arcnautical-mcp": {
"type": "http",
"url": "https://mcp.arcnautical.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
- Server version: 0.2.0 → 0.2.1 functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.arcnautical.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=arcnautical.com | CN=YE2,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 61f3b41ef7f1a1d06829f34ea3b32c881d5 |
| SANs: *.arcnautical.com, arcnautical.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.arcnautical.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| arcnautical.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.arcnautical.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.arcnautical.com/mcp | HTTPS enforced | 301 | https://mcp.arcnautical.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_vessel Check a vessel (no key) ~111
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).
| Name | Type | Req | Description |
|---|---|---|---|
| imo | string | yes | Seven-digit IMO number of the vessel |
| Name | Type | Req | Description |
|---|---|---|---|
| assessed | boolean | – | false means ownership and vetting are defaults, not findings |
| checkedAt | string | yes | ISO-8601 time the sources were read; designations change daily |
| fullReport | string | – | Human-readable report URL for this hull |
| imo | string | yes | The seven-digit IMO number screened |
| ownership | object | – | – |
| rate_limit | object | yes | Keyless allowance for the caller's address |
| sanctions | object | yes | – |
| vetting | object | – | – |
No examples provided.
find_port Find a port / UN/LOCODE (no key) ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches to return (default 5) |
| query | string | yes | Port name, country, or LOCODE fragment, e.g. "rotterdam", "NLRTM", "Piraeus" |
| Name | Type | Req | Description |
|---|---|---|---|
| ports | array | yes | Best matches first |
No examples provided.
get_screening Retrieve a screening record (API key) ~52
Fetch a stored screening record by id — the audit copy, retained ten years. Needs ARCNAUTICAL_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Screening id returned by screen_vessel or in a batch item |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No examples provided.
get_usage Usage and quota (API key) ~29
Live and test usage, remaining allowance, reset time, batch limits and monitor capacity for the configured key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| assessments | object | – | Allowance, used, remaining and reset per environment |
| environment | string | – | live | test |
| limits | object | – | – |
| screenings | object | – | – |
No examples provided.
score_voyage Score a voyage route (API key) ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_reference | string | – | Your own reference (voyage id, fixture); echoed on the assessment |
| destination | string | yes | 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 | yes | 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
No examples provided.
screen_vessel Screen a vessel (full record, API key) ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_reference | string | – | Your own reference (order id, voyage id); echoed on the record |
| imo | string | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No examples provided.
screen_vessels Screen up to 50 vessels (API key) ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| imos | array | yes | Up to 50 seven-digit IMO numbers |
| include_vetting | boolean | – | false skips the vetting grade for a faster sanctions-only screen |
| Name | Type | Req | Description |
|---|---|---|---|
| batch | object | yes | The batch as last read |
| items | array | yes | One row per hull |
No examples provided.
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 hosted endpoint (https://mcp.arcnautical.com/mcp).
Is the com.arcnautical/mcp server safe to use?
com.arcnautical/mcp scores 68 out of 100 on VerifyMCP. 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.
Does the com.arcnautical/mcp server require authentication?
No. We connected to com.arcnautical/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.