Enterprise DNA
M MCP Servers Developer low

tools-mcp/vessel-traffic-mcp

by Various

Read-only MCP server for vessel AIS, ship tracking, schedules, and BYOK maritime providers

T

MCP

tools-mcp/vessel-traffic-mcp

Added 7 June 2026

#ais #aishub #aisstream #byok #chatgpt-mcp #claude-mcp #codex-plugin #gemini-mcp

Overview

A read-only MCP server that provides vessel AIS data, ship tracking, schedules, and maritime information through bring-your-own-key providers. It exposes standardized tools for querying vessel positions, port calls, and maritime traffic via the Model Context Protocol.

Best for

Best for
Developers building AI agents or dashboards that need live maritime traffic data

Use cases

  • Integrate real-time vessel positions into a logistics dashboard
  • Query port schedules and estimated arrival times for supply chain planning
  • Monitor maritime traffic patterns for fleet management or analytics

Notes

A read-only MCP server that provides vessel AIS data, ship tracking, schedules, and maritime information through bring-your-own-key providers. It exposes standardized tools for querying vessel positions, port calls, and maritime traffic via the Model Context Protocol.

0 stars on GitHub. Last updated 2026-05-27. Licensed MIT.

Use cases

  • Integrate real-time vessel positions into a logistics dashboard
  • Query port schedules and estimated arrival times for supply chain planning
  • Monitor maritime traffic patterns for fleet management or analytics

Pros

  • Standard MCP interface makes it easy to connect with AI agents and assistants
  • BYOK model lets you use existing maritime data subscriptions without vendor lock-in
  • Read-only design reduces risk of accidental data modification

Cons

  • Requires a separate API key from a maritime data provider, adding setup overhead
  • No built-in caching or offline support, so queries depend on provider availability
  • Limited to read operations, cannot submit or update vessel data

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Standard MCP interface makes it easy to connect with AI agents and assistants
  • BYOK model lets you use existing maritime data subscriptions without vendor lock-in
  • Read-only design reduces risk of accidental data modification

Cons

  • Requires a separate API key from a maritime data provider, adding setup overhead
  • No built-in caching or offline support, so queries depend on provider availability
  • Limited to read operations, cannot submit or update vessel data