tools-mcp/vessel-traffic-mcp

English |
한국어 |
日本語 |
中文
**Vessel tracking and shipping schedules for AI agents.**
Vessel Traffic MCP is a read-only **Model Context Protocol (MCP) server**
for vessel identity lookup, AIS-style positions, tracks, port calls,
carrier schedules, vessel schedules, and delay heuristics. It gives
Claude, ChatGPT, Codex, MCP Inspector, and other MCP clients one
normalized maritime-data tool surface.
Use it when an agent needs to:
- search/fetch vessel context through generic connector-style MCP tools;
- resolve a vessel from a name, MMSI, IMO, callsign, or bill-of-lading text;
- ask where a vessel is, where it has been, or which vessels are in an area;
- search container-shipping schedules by port pair or vessel;
- return the original provider and source URL with every live/public result;
- test maritime workflows safely before buying paid AIS or schedule APIs.
The project does not bypass provider terms, paywalls, CAPTCHA, or access
controls. Commercial providers are Bring Your Own Key (BYOK), the default
test path is fixture-only, and this is not a navigation product.
Open source under the MIT license. Pre-1.0; APIs and tool
surfaces may change.
Contents
- Install In An MCP Client
- Agent Discovery Page
- What It Exposes
- Provider Model
- Responsible Use And Third-Party Rights
- Help Spread
- From Source
- Remote HTTP Setup
- Current Distribution
- Star History
- Shared Reference
Install In An MCP Client
For Claude Desktop, Claude Code, Codex CLI, Cursor, VS Code, or any
stdio MCP client, use the npm package:
Then restart the client and try:
Full client setup lives in
docs/runbooks/clients.md, and Codex
details live in docs/runbooks/codex.md.
Source-checkout config snippets are in
Shared MCP Config Snippets.
Marketplace and AI-client submission helpers live in
llms-install.md, LAUNCHGUIDE.md,
and assets/logo-400.png.
Agent Discovery Page
The public landing page for assistant-agent search and install snippets is:
https://tools-mcp.github.io/vessel-traffic-mcp/
Use that URL when sharing the project as a **vessel AIS MCP**, **ship tracking
MCP**, **ChatGPT MCP**, **Codex MCP**, **Claude MCP**, or **Gemini MCP** server.
The page includes a golden prompt for the EVER GIVEN scenario and client
snippets for local stdio and remote Streamable HTTP setup.
Assistant services do not automatically discover arbitrary MCP servers. The
operator must connect this MCP first; after that, the tool descriptions,
search/fetch wrappers, and vessel-specific tools give the agent a clear
path from a ship-name prompt to source-attributed results.
What It Exposes
| Area | Read-only tools |
| --- | --- |
| Search-style connector flow | search, fetch |
| Vessel identity | vessel_search, vessel_name_resolve, document_vessel_lookup |
| AIS-style movement | vessel_position, vessel_area, vessel_track |
| Port activity | port_calls |
| Shipping schedules | carrier_schedule_search, vessel_schedule, schedule_delay_predict |
| Provider setup | provider_status, data_sources, credential_profiles, provider_onboarding |
Every live or public-provider response must expose provenance:
source.provider and source.landingUrl. The project is designed to
route users back to the original service, not to hide or rebrand the
data source.
Provider Model
| Provider group | How it is enabled | Notes |
| --- | --- | --- |
| Fixture | default | deterministic tests and demos; no network, accounts, or API keys |
| Public opt-in | VESSEL_MCP_ENABLE_PUBLIC_PROVIDERS=myshiptracking,tradlinx,aisfriends | public web adapters with source attribution |
| BYOK commercial/community APIs | VESSEL_MCP_ENABLE_BYOK_PROVIDERS=... plus VESSEL_MCP_PROFILE_* env vars | user-owned credentials only; secrets are redacted from logs, errors, and MCP responses |
| Remote deployment | VESSEL_MCP_TRANSPORT=http | Streamable HTTP at /mcp; set VESSEL_MCP_AUTH_TOKEN for Authorization: Bearer |
Use the provider_onboarding MCP tool to inspect provider signup URLs,
required env vars, configured profile status, and validation steps. It
is read-only and never creates accounts, accepts terms, solves CAPTCHA,
completes email verification, sets payment details, or issues API keys.
Responsible Use And Third-Party Rights
This project is provided as open-source infrastructure for public-interest
interoperability, workflow testing, and source-attributed maritime data access.