Vessel Traffic MCP

What tools-mcp/vessel-traffic-mcp MCP server does

tools-mcp/vessel-traffic-mcp MCP server gives an agent a read-only interface to maritime information. It can identify vessels from names, MMSI numbers, IMO numbers, callsigns, or bill-of-lading text; retrieve current or historical movement data; inspect port activity; and search container-shipping schedules.

The server also provides generic search and fetch connector-style tools, along with provider-management tools that report status, data sources, credential profiles, and onboarding details. Results from live or public providers include source.provider and source.landingUrl, allowing an application or agent to identify and revisit the original source.

How it works

The distribution uses a provider model with three main operating paths. Fixture data is enabled by default for deterministic tests and demonstrations and does not make network requests. Public web adapters can be explicitly enabled, while commercial or community APIs use credentials supplied by the operator through provider-specific environment variables.

The server is read-only. Its onboarding tool can describe signup links, required variables, profile status, and validation steps, but it does not create accounts, accept provider terms, solve CAPTCHAs, verify email addresses, set payment details, or issue API keys. A remote deployment can expose Streamable HTTP at /mcp; local MCP clients can run the package over stdio.

Setup and configuration

Install tools-mcp/vessel-traffic-mcp MCP server from npm with npx -y @tools-mcp/vessel-traffic-mcp and configure it as a stdio server in a compatible MCP client. The example configuration sets VESSEL_MCP_TRANSPORT=stdio. Client documentation covers Claude Desktop, Claude Code, Codex CLI, Cursor, and VS Code.

To enable the documented public adapters, set VESSEL_MCP_ENABLE_PUBLIC_PROVIDERS to a comma-separated list such as myshiptracking,tradlinx,aisfriends. BYOK providers use VESSEL_MCP_ENABLE_BYOK_PROVIDERS together with provider profile variables. The README states that secrets are redacted from logs, errors, and MCP responses.

For remote HTTP operation, set VESSEL_MCP_TRANSPORT=http. VESSEL_MCP_AUTH_TOKEN can protect the endpoint using an Authorization: Bearer header. These settings are optional; fixture mode does not require credentials or external accounts.

Tools and capabilities

tools-mcp/vessel-traffic-mcp MCP server groups its read-only tools into the following areas:

• Search and retrieval: search, fetch
• Vessel identity: vessel_search, vessel_name_resolve, document_vessel_lookup
• Movement: vessel_position, vessel_area, vessel_track
• Port activity: port_calls
• Schedules: carrier_schedule_search, vessel_schedule, schedule_delay_predict
• Provider information: provider_status, data_sources, credential_profiles, provider_onboarding

Typical prompts include finding the current position of a named vessel with source fields included, or searching a carrier schedule between two ports. The package is intended for maritime-data workflows and testing, not as a navigation product.

Limitations and notes

Provider access remains subject to the provider's terms, rate limits, data licenses, account permissions, and applicable law. The project does not bypass paywalls, authentication, CAPTCHAs, robots policies, or other access controls. Public and commercial data availability depends on the enabled provider configuration. The project is pre-1.0, so its APIs and tool surface may change.

The repository is released under the MIT license. It does not grant permission to redistribute or rebrand third-party services, maps, databases, trademarks, copyrighted material, or provider responses.