Datalastic Vessel Tracking & Maritime Intelligence
v1.0.0Vessel tracking for 750,000+ ships, with ownership, inspections, port records, routes, and more.
Endpoint health
online- Last checked
- 11/20/2026, 6:17:32 AM
- Latency
- 328 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.datalastic%2Fvessel-tracking
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.datalastic/vessel-tracking": {
"url": "https://mcp.datalastic.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Estimate a vessel's current position (SAT-E)
estimated_vessel_position
Estimate where a vessel is right now when its last AIS position is stale — Datalastic uses terrestrial AIS only, so a ship in open ocean can be many hours old. The position is calculated from the last known fix, the recognized destination port, and the route-based ETA. It is an ESTIMATE, not an observed position. Tool selection — use this LAST: prefer get_vessel for a live position (cheapest); prefer get_vessel_pro when the user wants the ETA or recognized destination. Only reach for this tool when BOTH hold: (1) a prior get_vessel/get_vessel_pro lookup shows the last known position is old, and (2) the vessel has a destination and an ETA. It is the heaviest call (it builds a route) and adds nothing when get_vessel already returns a recent position. Because it is an estimate, OFFER it to the user first rather than calling it silently, and when you present the result make clear it is an estimated position, not a real fix. If estimated_position equals the last known lat/lon, the system could not extrapolate (the position is recent, or the ETA is missing/outdated) — say so instead of implying movement.
Schema valid · SHA-256 f8f0fd5501e6…
View input schema
{ "type": "object", "properties": { "mmsi": { "type": "string", "description": "Vessel MMSI identifier, exactly 9 digits. Provide exactly one of mmsi, imo, or uuid." }, "imo": { "type": "string", "description": "Vessel IMO number, exactly 7 digits. Provide exactly one of mmsi, imo, or uuid." }, "uuid": { "type": "string", "description": "Datalastic internal vessel UUID. Provide exactly one of mmsi, imo, or uuid." } }, "additionalProperties": false }Search for ports
find_ports
Search the port registry and return matching ports (identity, country, UN/LOCODE, classification, coordinates, maritime area). Search by name (optionally fuzzy), UN/LOCODE, classification, country, or geographically (lat + lon + radius in nautical miles). Always returns a list, even for a single match. Use this to discover ports or resolve a name to a UN/LOCODE/uuid; for full detail on one known port (including terminals) use get_port.
Connections
streamable-http
https://mcp.datalastic.com/mcp