Log inSubmit server
Vessel Traffic MCP logo

Vessel Traffic MCP

by tools-mcp

Read-only MCP tools for vessel identity, positions, tracks, port calls, schedules, and source-attributed maritime data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Vessel Traffic MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tools-mcp-vessel-traffic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tools-mcp/vessel-traffic-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @tools-mcp/vessel-traffic-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 27d ago.

Overview

tools-mcp/vessel-traffic-mcp MCP server exposes read-only maritime data tools for vessel identity, AIS-style movement, port calls, shipping schedules, and delay heuristics. It normalizes fixture, public opt-in, and user-configured provider data through MCP, while preserving the provider name and source URL in live responses. Use it for shipping workflows that need vessel context or schedule lookups without writing to external systems. Commercial providers require your own credentials, while the default fixture mode works without network access or API keys.

Use cases

  • Resolve a vessel from its name, IMO, MMSI, or callsign
  • Track vessel positions and historical movement
  • Inspect port calls for a vessel
  • Search carrier schedules between ports
  • Test maritime agent workflows with fixture data

Key features

  • Read-only vessel identity lookup
  • AIS-style positions, areas, and tracks
  • Port call and shipping schedule searches
  • Schedule delay heuristics
  • Fixture, public, and BYOK provider modes
  • Provider and source attribution

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

17/18 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @tools-mcp/vessel-traffic-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars8Stargazers on the source repository.
npm downloads214Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Vessel Traffic MCP works

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.

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Vessel Traffic MCP

Configure an MCP client to run `npx -y @tools-mcp/vessel-traffic-mcp` over stdio, then restart the client.

Yes. The README provides stdio installation guidance for Claude Desktop and other MCP clients.

No key is required for the default fixture mode. Public adapters are opt-in, and commercial or community providers require user-owned credentials.

It supports vessel identity, positions, areas, tracks, port calls, carrier schedules, vessel schedules, and delay heuristics.

Yes. Set `VESSEL_MCP_TRANSPORT=http` for Streamable HTTP at `/mcp`; `VESSEL_MCP_AUTH_TOKEN` can be used for bearer-token authorization.

Related MCP servers

All in Location Services All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewVessel Traffic MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tools-mcp-vessel-traffic-mcp?style=directory)](https://allmcps.com/mcp/tools-mcp-vessel-traffic-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/tools-mcp-vessel-traffic-mcp"><img src="https://allmcps.com/api/badge/tools-mcp-vessel-traffic-mcp?style=directory" alt="Vessel Traffic MCP on AllMCPs" /></a>