A
licenseNot graded
qualityD
maintenanceA fully MCP-compliant, open-source maritime data service that provides real-time vessel tracking, port information, route planning, and weather/tide data for maritime applications.
14
MIT
Chuk MCP Maritime Archives
by IBM
Related Servers
Alternatives to Chuk MCP Maritime Archives
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceAn MCP server for indexing and searching Commodore 64 documentation using full-text, semantic, and fuzzy search across multiple file formats. It enables RAG-based question answering, entity extraction, and interactive timeline or knowledge graph visualizations.941-
- AlicenseNot gradedqualityDmaintenanceMCP server for maritime compliance, enabling natural-language checks on MARPOL Annex VI, EU ETS, CII/EEXI, IMDG, bunker fuel, ballast water, and Port State Control inspection prep.23 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI assistants to access real-time vessel tracking, port information, and maritime data through the Datalastic Marine AIS Data API.1MIT
- AlicenseAqualityCmaintenanceAn MCP server designed for interacting with the Model Context Protocol Registry API to discover and retrieve information about available MCP servers. It provides tools to search, list, and view detailed configurations and version history for servers within the registry.4MIT
- AlicenseAqualityBmaintenanceRead-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.1438 npm6MIT
TDQS
A4.4/5.0
Scored across 47 tools
Disambiguation4/5
Tools are largely distinct by entity type (search, get, aggregate, compare) but there is minor overlap between single-voyage and aggregate speed/tortuosity tools. However, detailed descriptions mitigate confusion.
Naming Consistency5/5
All tools follow a consistent 'maritime_verb_noun' pattern (e.g., maritime_search_voyages, maritime_aggregate_track_speeds). The naming is predictable and uniform.
Tool Count4/5
47 tools is high but justifiable for a comprehensive maritime archives server covering voyages, wrecks, crew, cargo, tracks, routes, and analysis. A few tools could be merged (e.g., export functions) but overall scope supports the count.
Completeness5/5
The tool surface covers all major operations expected for historical maritime research: search, retrieve details, aggregate, compare, export, and specialized analysis (speed, tortuosity, wind, DID tests). No obvious gaps in the domain.
Maintenance
ActivitySlowing
ResponsivenessNo issues