Maritime Vessel Data MCP Server
Related Servers
Alternatives to Maritime Vessel Data MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables real-time vessel tracking, port data, maritime weather, and maritime intelligence through 25 tools, allowing AI clients to query live vessel positions, registry, port info, area searches, weather, and more.MIT- AlicenseAqualityDmaintenanceRead-only MCP server for vessel identity lookup, AIS-style positions, tracks, port calls, carrier schedules, vessel schedules, and delay heuristics with source attribution and BYOK provider support.1448 npm8MIT
- AlicenseNot gradedqualityCmaintenanceAccess Global Fishing Watch data from any MCP-compatible AI assistant or terminal: search vessels, retrieve fishing activity and port events, look up marine regions, and compute aggregate statistics.22 npm2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables vessel screening by IMO number for sanctions matches, ownership opacity, and A–E vetting grades, along with batch screening and retrieval of stored records. Also resolves port names or countries to UN/LOCODEs and scores voyage risk between two ports.65 npmMIT
- AlicenseAqualityDmaintenanceProvides maritime routing capabilities, enabling computation of oceangoing route distances and full routes in GeoJSON format via MCP tools.310MIT
- AlicenseNot gradedqualityCmaintenanceProvides live AIS vessel positions from datalastic.com, enabling querying of vessel data through natural language via the Pipeworx MCP gateway.80 npmMIT
TDQS
Scored across 14 tools
Each tool targets a clearly distinct resource or analytical question: vessel search, nearby vessels, area/watched filters, single/fleet tracks, region subscription, and derived metrics like passage time, port calls, congestion, density, and anchorages. Even the geographically overlapping tools are differentiated by their exact filter semantics and described with enough precision to prevent misselection.
Names are readable and consistently snake_case, but the pattern is mixed: some are verb-first (search_vessels, list_regions, set_regions) while most are descriptive noun phrases (vessel_track, port_calls, traffic_density, anchorages). There is no single consistent convention, though the names remain self-explanatory.
Fourteen tools is within the ideal range and each tool earns its place: discovery, details, tracks, region subscription, and specialized maritime analytics are all represented without redundant or filler tools. The count matches the breadth of the domain well.
The server covers the full read-only AIS workflow: finding vessels, retrieving details, viewing current positions and historical tracks, managing region subscriptions, and producing derived insights like passage times, port calls, congestion, traffic density, and anchorages. No obvious dead ends or missing operations are apparent for its stated purpose.