MCP server for the ArcNautical API: screen any vessel by IMO for sanctions, ownership opacity and vetting grade. Two tools need no API key.
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Documented (README)
claude mcp add arcnautical-mcp -- npx -y @arcnautical/mcp{
"mcpServers": {
"arcnautical-mcp": {
"command": "npx",
"args": ["-y", "@arcnautical/mcp"]
}
}
}Resumen de MCP Servers
# @arcnautical/mcp
An [MCP](https://modelcontextprotocol.io) server for the [ArcNautical API](https://arcnautical.com/developers/): screen any commercial vessel by IMO number for sanctions, ownership opacity and a vetting grade — from Claude, ChatGPT, Cursor, VS Code, Windsurf or any MCP client.
**Two tools need no API key at all.** Install it, ask "is IMO 9274446 sanctioned?", get the answer.
```
IMO 9274446 HS STAR: sanctions RED — 4 confirmed matches on vessel identifier.
Ownership opacity MEDIUM. Vetting grade E (unacceptable). Checked 2026-09-12T08:10:40Z.
```
## Install
Requires Node 18+. No install step — every client below runs it with `npx`.
**Claude Desktop** — `claude_desktop_config.json`:
```json
{
"mcpServers": {
"arcnautical": {
"command": "npx",
"args": ["-y", "@arcnautical/mcp"]
}
}
}
```
**Claude Code**
```
claude mcp add arcnautical -- npx -y @arcnautical/mcp
```
**Cursor / Windsurf / VS Code** — same `command` / `args` shape in the client's MCP settings.
To unlock the full record, batches and voyage scoring, add an API key to the `env` block:
```json
{
"mcpServers": {
"arcnautical": {
"command": "npx",
"args": ["-y", "@arcnautical/mcp"],
"env": { "ARCNAUTICAL_API_KEY": "arc_live_…" }
}
}
}
```
Keys are self-serve at https://arcnautical.com/arcnautical.html#/developer-api — no approval step. A key includes 5,000 vessel screenings and 10,000 voyage assessments a month.
## Tools
| Tool | Key? | What it does |
|---|---|---|
| `check_vessel` | no | Sanctions status (OFAC SDN, EU, UN, UK OFSI, OpenSanctions), ownership-opacity score, A–E vetting grade for one IMO. 100/hour per IP. |
| `find_port` | no | Resolve a port name or country to UN/LOCODEs — call before `score_voyage`. |
| `screen_vessel` | yes | The full screening record: every match with its source list, programme and confidence class, the graded vetting factors, per-source freshness, a retained record id. Same hull asked again today replays free. |
| `screen_vessels` | yes | Batch up to 50 IMOs and wait for the results. |
| `get_screening` | yes | Retrieve a stored record by id (retained ten years). |
| `score_voyage` | yes | Route risk between two LOCODEs: score, level, drivers, confidence, missing sources. |
| `get_usage` | yes | Remaining allowance and limits for the configured key. |
### Reading a verdict
- **RED** — confirmed match on the vessel identifier. **AMBER** — possible match, review it. **GREEN** — no match against the sources reached. **INCOMPLETE** — a core source could not be read; never present it as clear.
- `coverage_complete: false` on a GREEN means one supplementary list was unavailable: re-screen before relying on it.
- `assessed: false` means ownership and vetting are defaults, not findings.
- The keyless check matches the vessel's **current** name and identifiers only. A hull renamed after a designation can read GREEN there; `screen_vessel` covers that case.
- Designations change daily. Quote the `checkedAt` / `screened_at` time with any answer.
## Idempotency
Every resource-creating call sends an `Idempotency-Key` derived from the *question* — the hull and the UTC day — not from the attempt. Asking about the same vessel twice in a day returns the stored record and spends nothing. The API's docs measured 42% of one integration's monthly screenings as same-day repeats billed only because their client generated a random key per call; this server does not do that.
## Environment
| Variable | Default | Purpose |
|---|---|---|
| `ARCNAUTICAL_API_KEY` | unset | Enables the keyed tools. |
| `ARCNAUTICAL_BASE_URL` | `https://arcnautical.com` | Override for testing. |
## Links
- Guide: https://arcnautical.com/developers/
- Reference: https://arcnautical.com/developers/reference/
- OpenAPI 3.1: https://arcnautical.com/api/v1/openapi.json
- Postman: https://www.postman.com/arcnautical-6322764/arcnautical-s-workspace/collection/u7ua5ow/arcnautical-api-v1
- For agents: https://arcnautical.com/llms.txt
## Development
```
npm install
npm test # builds, then drives dist/cli.js over stdio against the live keyless endpoints
```
MIT © ArcNautical
Lo que la gente pregunta sobre arcnautical-mcp
¿Qué es SaltyTaro/arcnautical-mcp?
+
SaltyTaro/arcnautical-mcp es mcp servers para el ecosistema de Claude AI. MCP server for the ArcNautical API: screen any vessel by IMO for sanctions, ownership opacity and vetting grade. Two tools need no API key. Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-09-12.
¿Cómo se instala arcnautical-mcp?
+
Puedes instalar arcnautical-mcp clonando el repositorio (https://github.com/SaltyTaro/arcnautical-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar SaltyTaro/arcnautical-mcp?
+
Nuestro agente de seguridad ha analizado SaltyTaro/arcnautical-mcp y le ha asignado un Trust Score de 87/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.
¿Quién mantiene SaltyTaro/arcnautical-mcp?
+
SaltyTaro/arcnautical-mcp es mantenido por SaltyTaro. La última actividad registrada en GitHub es del 2026-09-12, con 0 issues abiertos.
¿Hay alternativas a arcnautical-mcp?
+
Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.
Despliega arcnautical-mcp en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/saltytaro-arcnautical-mcp)<a href="https://claudewave.com/repo/saltytaro-arcnautical-mcp"><img src="https://claudewave.com/api/badge/saltytaro-arcnautical-mcp" alt="Featured on ClaudeWave: SaltyTaro/arcnautical-mcp" width="320" height="64" /></a>Más MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!
The fastest path to AI-powered full stack observability, even for lean teams.