Datalastic Vessel Tracking & Maritime Intelligence

Official25 toolsLive

by datalastic

Vessel tracking for 750,000+ ships, with ownership, inspections, port records, routes, and more.

Datalastic Vessel Tracking MCP Server (com.datalastic/vessel-tracking)

The com.datalastic/vessel-tracking MCP server provides vessel tracking covering 750,000+ ships, including ownership, inspections, port records, routes, and related information. It is an official Model Context Protocol (MCP) server intended for use with any MCP-compatible AI client.

🛠️ Key Features

Real-time vessel tracking for 750,000+ ships
Data includes ownership, inspections, port records, and routes
Exposes 25 tools across six categories

🚀 Use Cases

Maritime intelligence queries that require live positions and historical/structured context
Enrichment of AI workflows with port data and vessel-related records

⚡ Developer Benefits

MCP-compatible interface for integrating maritime context into AI clients
Tool-based access to vessel tracking and maritime intelligence data

⚠️ Limitations

Tool coverage is described only as 25 tools across six categories; specific tool names and category details are not included in the provided data

Topics

aismaritimemaritime-intelligencemcpmcp-servermodel-context-protocolvessel-tracking

Captured live from the server via tools/list.

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.

Parameters3

mmsi	string	optional	Vessel MMSI identifier, exactly 9 digits. Provide exactly one of mmsi, imo, or uuid.
imo	string	optional	Vessel IMO number, exactly 7 digits. Provide exactly one of mmsi, imo, or uuid.
uuid	string	optional	Datalastic internal vessel UUID. Provide exactly one of mmsi, imo, or uuid.

Raw 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
}

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.

Parameters9

name	string	optional	Port name to search for (set fuzzy for approximate matching).
uuid	string	optional	Datalastic port UUID.
fuzzy	boolean	optional	Match the name approximately instead of exactly.
port_type	string	optional	Filter by classification. One of: Port, Anchorage, Marina, Offshore Terminal, Shelter, Demolition Yard, Canal, Fishing Harbour.
country_iso	string	optional	2-letter ISO country code (e.g. GB).
unlocode	string	optional	Port UN/LOCODE: 5 alphanumeric characters (case-insensitive).
lat	null \| number	optional	Center latitude for a geographic search (use with lon and radius).
lon	null \| number	optional	Center longitude for a geographic search (use with lat and radius).
radius	number	optional	Search radius in nautical miles (max 50); requires lat and lon.

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Port name to search for (set fuzzy for approximate matching)."
    },
    "uuid": {
      "type": "string",
      "description": "Datalastic port UUID."
    },
    "fuzzy": {
      "type": "boolean",
      "description": "Match the name approximately instead of exactly."
    },
    "port_type": {
      "type": "string",
      "description": "Filter by classification. One of: Port, Anchorage, Marina, Offshore Terminal, Shelter, Demolition Yard, Canal, Fishing Harbour."
    },
    "country_iso": {
      "type": "string",
      "description": "2-letter ISO country code (e.g. GB)."
    },
    "unlocode": {
      "type": "string",
      "description": "Port UN/LOCODE: 5 alphanumeric characters (case-insensitive)."
    },
    "lat": {
      "type": [
        "null",
        "number"
      ],
      "description": "Center latitude for a geographic search (use with lon and radius)."
    },
    "lon": {
      "type": [
        "null",
        "number"
      ],
      "description": "Center longitude for a geographic search (use with lat and radius)."
    },
    "radius": {
      "type": "number",
      "description": "Search radius in nautical miles (max 50); requires lat and lon."
    }
  },
  "additionalProperties": false
}

find_vessels

Search the vessel registry by any combination of name (optionally fuzzy), type, flag country, dimensions, tonnage, or year built — no MMSI or IMO needed. Returns up to 500 static specification records per page (tonnage, dimensions, year built, home port, callsign, etc.) — this is reference data, NOT live position. Provide at least one search criterion; use the response's next token via the next argument to page. Credits: 1 per vessel found. For a vessel's live position use get_vessel; for vessels currently in an area use get_vessels_in_radius.

Parameters17

name	string	optional	Vessel name to search for. Combine with fuzzy for similar-name matching.
fuzzy	boolean	optional	If true, match similar/approximate names; if false (default) the name must match exactly. Only meaningful together with name.
type	string	optional	Filter by vessel type (e.g. Cargo, Tanker).
type_specific	string	optional	Filter by vessel subtype (e.g. Bulk Carrier).
country_iso	string	optional	Filter by flag country, 2-letter ISO code (e.g. MT).
gross_tonnage_min	null \| integer	optional	Minimum gross tonnage.
gross_tonnage_max	null \| integer	optional	Maximum gross tonnage.
deadweight_min	null \| integer	optional	Minimum deadweight (tonnes).
deadweight_max	null \| integer	optional	Maximum deadweight (tonnes).
length_min	null \| number	optional	Minimum length (meters).
length_max	null \| number	optional	Maximum length (meters).
breadth_min	null \| number	optional	Minimum breadth (meters).
breadth_max	null \| number	optional	Maximum breadth (meters).
year_built_min	null \| integer	optional	Earliest year built.
year_built_max	null \| integer	optional	Latest year built.
include_unknown_type	null \| boolean	optional	Include vessels with no/unknown type. Maps to the API's _empty_.
next	string	optional	Pagination token from a previous response's next field, to fetch the next page (up to 500 results per page).

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Vessel name to search for. Combine with fuzzy for similar-name matching."
    },
    "fuzzy": {
      "type": "boolean",
      "description": "If true, match similar/approximate names; if false (default) the name must match exactly. Only meaningful together with name."
    },
    "type": {
      "type": "string",
      "description": "Filter by vessel type (e.g. Cargo, Tanker)."
    },
    "type_specific": {
      "type": "string",
      "description": "Filter by vessel subtype (e.g. Bulk Carrier)."
    },
    "country_iso": {
      "type": "string",
      "description": "Filter by flag country, 2-letter ISO code (e.g. MT)."
    },
    "gross_tonnage_min": {
      "type": [
        "null",
        "integer"
      ],
      "description": "Minimum gross tonnage."
    },
    "gross_tonnage_max": {
      "type": [
        "null",
        "integer"
      ],
      "description": "Maximum gross tonnage."
    },
    "deadweight_min": {
      "type": [
        "null",
        "integer"
      ],
      "description": "Minimum deadweight (tonnes)."
    },
    "deadweight_max": {
      "type": [
        "null",
        "integer"
      ],
      "description": "Maximum deadweight (tonnes)."
    },
    "length_min": {
      "type": [
        "null",
        "number"
      ],
      "description": "Minimum length (meters)."
    },
    "length_max": {
      "type": [
        "null",
        "number"
      ],
      "description": "Maximum length (meters)."
    },
    "breadth_min": {
      "type": [
        "null",
        "number"
      ],
      "description": "Minimum breadth (meters)."
    },
    "breadth_max": {
      "type": [
        "null",
        "number"
      ],
      "description": "Maximum breadth (meters)."
    },
    "year_built_min": {
      "type": [
        "null",
        "integer"
      ],
      "description": "Earliest year built."
    },
    "year_built_max": {
      "type": [
        "null",
        "integer"
      ],
      "description": "Latest year built."
    },
    "include_unknown_type": {
      "type": [
        "null",
        "boolean"
      ],
      "description": "Include vessels with no/unknown type. Maps to the API's _empty_."
    },
    "next": {
      "type": "string",
      "description": "Pagination token from a previous response's next field, to fetch the next page (up to 500 results per page)."
    }
  },
  "additionalProperties": false
}

get_port

Return detailed information for a single port — identity, country, UN/LOCODE, classification, coordinates, maritime area, and the list of terminals (name, operating company, coordinates, address, website). Look up the port by its Datalastic uuid or its UN/LOCODE (exactly one). To search for a port by name or location, or when you don't have an exact identifier, use find_ports first.

Parameters2

uuid	string	optional	Datalastic port UUID. Provide exactly one of uuid or unlocode.
unlocode	string	optional	Port UN/LOCODE: 5 alphanumeric characters, e.g. ESMPG (case-insensitive). Provide exactly one of uuid or unlocode.

Raw schema

{
  "type": "object",
  "properties": {
    "uuid": {
      "type": "string",
      "description": "Datalastic port UUID. Provide exactly one of uuid or unlocode."
    },
    "unlocode": {
      "type": "string",
      "description": "Port UN/LOCODE: 5 alphanumeric characters, e.g. ESMPG (case-insensitive). Provide exactly one of uuid or unlocode."
    }
  },
  "additionalProperties": false
}

get_vessel

Return the current position and basic information for a single vessel, identified by exactly one of: MMSI (9 digits), IMO (7 digits), or Datalastic UUID. Includes live coordinates, speed, course, heading, navigation status and the raw AIS destination text. This is the default tool for vessel lookups. For the recognized destination or origin port (name + UNLOCODE), actual departure time (ATD), a reliable estimated time of arrival (ETA), or draught, use get_vessel_pro instead.

Parameters3

mmsi	string	optional	Vessel MMSI identifier, exactly 9 digits (e.g. 477553000). Provide exactly one of mmsi, imo, or uuid.
imo	string	optional	Vessel IMO number, exactly 7 digits (e.g. 9839179). Provide exactly one of mmsi, imo, or uuid.
uuid	string	optional	Datalastic internal vessel UUID. Provide exactly one of mmsi, imo, or uuid.

Raw schema

{
  "type": "object",
  "properties": {
    "mmsi": {
      "type": "string",
      "description": "Vessel MMSI identifier, exactly 9 digits (e.g. 477553000). Provide exactly one of mmsi, imo, or uuid."
    },
    "imo": {
      "type": "string",
      "description": "Vessel IMO number, exactly 7 digits (e.g. 9839179). 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
}

get_vessel_history

Return the historical track (ordered position records) for a single vessel, identified by exactly one of: MMSI (9 digits), IMO (7 digits), or Datalastic UUID. Specify the time range with either 'days' (last N days) or 'from'/'to' dates (YYYY-MM-DD, 'to' at most 30 days after 'from'). Data is available since 2021-08-10; only position changes are stored, so stationary periods may have gaps.

Parameters6

mmsi	string	optional	Vessel MMSI identifier, exactly 9 digits. Provide exactly one of mmsi, imo, or uuid.
imo	string	optional	Vessel IMO number, exactly 7 digits. Provide exactly one of mmsi, imo, or uuid.
uuid	string	optional	Datalastic internal vessel UUID. Provide exactly one of mmsi, imo, or uuid.
days	integer	optional	Number of past days from today to include (e.g. 3). Use either days OR from/to, not both.
from	string	optional	Start date YYYY-MM-DD. Data is available since 2021-08-10. Use either from/to OR days, not both.
to	string	optional	End date YYYY-MM-DD (at most 30 days after 'from'). Requires 'from'. Defaults to now if omitted.

Raw 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."
    },
    "days": {
      "type": "integer",
      "description": "Number of past days from today to include (e.g. 3). Use either days OR from/to, not both."
    },
    "from": {
      "type": "string",
      "description": "Start date YYYY-MM-DD. Data is available since 2021-08-10. Use either from/to OR days, not both."
    },
    "to": {
      "type": "string",
      "description": "End date YYYY-MM-DD (at most 30 days after 'from'). Requires 'from'. Defaults to now if omitted."
    }
  },
  "additionalProperties": false
}

get_vessel_info

Return static specifications for a single vessel, identified by exactly one of: MMSI (9 digits), IMO (7 digits), or Datalastic UUID. Includes physical dimensions (length, breadth, draught), tonnage and cargo capacity (gross tonnage, deadweight, TEU, liquid gas), speed characteristics, year built, flag country, callsign and home port. This is reference data, NOT live position — use get_vessel for the current position, or find_vessels to search the registry by attributes.

Parameters3

mmsi	string	optional	Vessel MMSI identifier, exactly 9 digits (e.g. 566093000). Provide exactly one of mmsi, imo, or uuid.
imo	string	optional	Vessel IMO number, exactly 7 digits (e.g. 9525338). Provide exactly one of mmsi, imo, or uuid.
uuid	string	optional	Datalastic internal vessel UUID. Provide exactly one of mmsi, imo, or uuid.

Raw schema

{
  "type": "object",
  "properties": {
    "mmsi": {
      "type": "string",
      "description": "Vessel MMSI identifier, exactly 9 digits (e.g. 566093000). Provide exactly one of mmsi, imo, or uuid."
    },
    "imo": {
      "type": "string",
      "description": "Vessel IMO number, exactly 7 digits (e.g. 9525338). 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
}

get_vessel_pro

Richer, heavier variant of get_vessel for a single vessel, identified by exactly one of: MMSI (9 digits), IMO (7 digits), or Datalastic UUID. In addition to the basic position and identity, it returns the recognized destination port and origin port (name + UNLOCODE), the actual time of departure (ATD), a reliable estimated time of arrival (ETA), and current draught. Prefer get_vessel for ordinary position or identity lookups; use get_vessel_pro only when the user asks about the destination or origin port, departure time, arrival time or ETA, or draught, as it is heavier on the backend. If the last known position is stale (the vessel may be out of terrestrial AIS range) and it has a destination and ETA, consider offering estimated_vessel_position to estimate where it is now.

Parameters3

mmsi	string	optional	Vessel MMSI identifier, exactly 9 digits (e.g. 477553000). Provide exactly one of mmsi, imo, or uuid.
imo	string	optional	Vessel IMO number, exactly 7 digits (e.g. 9839179). Provide exactly one of mmsi, imo, or uuid.
uuid	string	optional	Datalastic internal vessel UUID. Provide exactly one of mmsi, imo, or uuid.

Raw schema

{
  "type": "object",
  "properties": {
    "mmsi": {
      "type": "string",
      "description": "Vessel MMSI identifier, exactly 9 digits (e.g. 477553000). Provide exactly one of mmsi, imo, or uuid."
    },
    "imo": {
      "type": "string",
      "description": "Vessel IMO number, exactly 7 digits (e.g. 9839179). 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
}

get_vessels_bulk

Return the current position and basic information for many vessels in a single call — supply any mix of MMSI, IMO and UUID lists, up to 100 identifiers in total. Each result has the same fields as get_vessel. Only successfully found vessels are returned (the response includes how many were found). Use this instead of many get_vessel calls when looking up a known set of vessels; for a single vessel use get_vessel.

Parameters3

mmsi	null \| array	optional	List of vessel MMSI identifiers (each exactly 9 digits).
imo	null \| array	optional	List of vessel IMO numbers (each exactly 7 digits).
uuid	null \| array	optional	List of Datalastic vessel UUIDs.

Raw schema

{
  "type": "object",
  "properties": {
    "mmsi": {
      "type": [
        "null",
        "array"
      ],
      "items": {
        "type": "string"
      },
      "description": "List of vessel MMSI identifiers (each exactly 9 digits)."
    },
    "imo": {
      "type": [
        "null",
        "array"
      ],
      "items": {
        "type": "string"
      },
      "description": "List of vessel IMO numbers (each exactly 7 digits)."
    },
    "uuid": {
      "type": [
        "null",
        "array"
      ],
      "items": {
        "type": "string"
      },
      "description": "List of Datalastic vessel UUIDs."
    }
  },
  "additionalProperties": false
}

get_vessels_in_radius

Scan a circular area and return all vessels currently within a given radius (nautical miles, greater than 0 and at most 50). Specify the center in exactly one way: lat+lon coordinates, a port (port_unlocode or port_uuid), or a vessel to center on (mmsi/imo/uuid). Optional filters: type, type_specific, exclude, nav_status, and include_unknown_type. Returns up to 500 vessels per page, each with its distance (nautical miles) from the center; if more remain, pass the response's 'next' token via the 'next' argument to page through them. Credits are charged per vessel found.

Parameters14

lat	null \| number	optional	Center latitude (-90..90). Must be used together with lon. Provide exactly one center: lat+lon, a port, or a vessel identifier.
lon	null \| number	optional	Center longitude (-180..180). Must be used together with lat.
port_unlocode	string	optional	Center the scan on a port, by UN/LOCODE (e.g. ESVLC).
port_uuid	string	optional	Center the scan on a port, by Datalastic port UUID.
mmsi	string	optional	Center the scan on a vessel, by MMSI (exactly 9 digits).
imo	string	optional	Center the scan on a vessel, by IMO (exactly 7 digits).
uuid	string	optional	Center the scan on a vessel, by Datalastic vessel UUID.
radius	number	required	Required. Scan radius in nautical miles, greater than 0 and at most 50.
type	string	optional	Optional: only include vessels of this type (e.g. Tanker, Cargo).
type_specific	string	optional	Optional: only include vessels of this specific subtype (e.g. LPG Tanker).
exclude	string	optional	Optional: exclude vessels of this type.
nav_status	null \| integer	optional	Optional: filter by AIS navigational status number (e.g. 0 = under way using engine).
include_unknown_type	null \| boolean	optional	Optional: include vessels that have no/unknown type. Defaults to the API default when omitted.
next	string	optional	Optional: pagination token from a previous response's 'next' field, to fetch the next page (up to 500 vessels per page).

Raw schema

{
  "type": "object",
  "properties": {
    "lat": {
      "type": [
        "null",
        "number"
      ],
      "description": "Center latitude (-90..90). Must be used together with lon. Provide exactly one center: lat+lon, a port, or a vessel identifier."
    },
    "lon": {
      "type": [
        "null",
        "number"
      ],
      "description": "Center longitude (-180..180). Must be used together with lat."
    },
    "port_unlocode": {
      "type": "string",
      "description": "Center the scan on a port, by UN/LOCODE (e.g. ESVLC)."
    },
    "port_uuid": {
      "type": "string",
      "description": "Center the scan on a port, by Datalastic port UUID."
    },
    "mmsi": {
      "type": "string",
      "description": "Center the scan on a vessel, by MMSI (exactly 9 digits)."
    },
    "imo": {
      "type": "string",
      "description": "Center the scan on a vessel, by IMO (exactly 7 digits)."
    },
    "uuid": {
      "type": "string",
      "description": "Center the scan on a vessel, by Datalastic vessel UUID."
    },
    "radius": {
      "type": "number",
      "description": "Required. Scan radius in nautical miles, greater than 0 and at most 50."
    },
    "type": {
      "type": "string",
      "description": "Optional: only include vessels of this type (e.g. Tanker, Cargo)."
    },
    "type_specific": {
      "type": "string",
      "description": "Optional: only include vessels of this specific subtype (e.g. LPG Tanker)."
    },
    "exclude": {
      "type": "string",
      "description": "Optional: exclude vessels of this type."
    },
    "nav_status": {
      "type": [
        "null",
        "integer"
      ],
      "description": "Optional: filter by AIS navigational status number (e.g. 0 = under way using engine)."
    },
    "include_unknown_type": {
      "type": [
        "null",
        "boolean"
      ],
      "description": "Optional: include vessels that have no/unknown type. Defaults to the API default when omitted."
    },
    "next": {
      "type": "string",
      "description": "Optional: pagination token from a previous response's 'next' field, to fetch the next page (up to 500 vessels per page)."
    }
  },
  "required": [
    "radius"
  ],
  "additionalProperties": false
}

get_weather

Return weather for one location: marine conditions (wave height/direction/period, swell, sea-surface temperature, ocean currents, sea level, …) plus general atmospheric conditions (air temperature, precipitation, wind speed/direction/gusts, humidity, cloud cover, visibility, pressure, weather code, …). Specify the location as exactly one of: coordinates (lat+lon), a vessel (mmsi/imo/uuid — weather near its last known position), or a port (port_unlocode/port_uuid). Use mode to choose current conditions (default), a 7-day daily forecast, a 7-day hourly forecast, or any combination. Each weather field has a matching entry in the corresponding *_units object.

Parameters8

lat	null \| number	optional	Latitude of the location (use together with lon).
lon	null \| number	optional	Longitude of the location (use together with lat).
mmsi	string	optional	Weather near this vessel by MMSI (9 digits).
imo	string	optional	Weather near this vessel by IMO (7 digits).
uuid	string	optional	Weather near this vessel by Datalastic UUID.
port_unlocode	string	optional	Weather near this port by UN/LOCODE (5 alphanumeric, case-insensitive).
port_uuid	string	optional	Weather near this port by Datalastic port UUID.
mode	null \| array	optional	Forecast mode(s); omit for current. One or more of: current (now), daily (7-day daily forecast), hourly (7-day hourly forecast). Combine for several at once.

Raw schema

{
  "type": "object",
  "properties": {
    "lat": {
      "type": [
        "null",
        "number"
      ],
      "description": "Latitude of the location (use together with lon)."
    },
    "lon": {
      "type": [
        "null",
        "number"
      ],
      "description": "Longitude of the location (use together with lat)."
    },
    "mmsi": {
      "type": "string",
      "description": "Weather near this vessel by MMSI (9 digits)."
    },
    "imo": {
      "type": "string",
      "description": "Weather near this vessel by IMO (7 digits)."
    },
    "uuid": {
      "type": "string",
      "description": "Weather near this vessel by Datalastic UUID."
    },
    "port_unlocode": {
      "type": "string",
      "description": "Weather near this port by UN/LOCODE (5 alphanumeric, case-insensitive)."
    },
    "port_uuid": {
      "type": "string",
      "description": "Weather near this port by Datalastic port UUID."
    },
    "mode": {
      "type": [
        "null",
        "array"
      ],
      "items": {
        "type": "string"
      },
      "description": "Forecast mode(s); omit for current. One or more of: current (now), daily (7-day daily forecast), hourly (7-day hourly forecast). Combine for several at once."
    }
  },
  "additionalProperties": false
}

intel_casualties

Retrieve a vessel's recorded maritime incidents — groundings, collisions, fires, machinery breakdowns, detentions and similar events — each with a date, category and a narrative description. Useful for risk and condition assessment. Identify the vessel by imo or name, and optionally bound the period with from / to. Part of the Maritime Reports add-on.

Parameters4

imo	string	optional	Vessel IMO number (exactly 7 digits) to look up.
name	string	optional	Vessel name to look up (use when the IMO is unknown).
from	string	optional	Only include incidents on or after this date (YYYY-MM-DD).
to	string	optional	Only include incidents on or before this date (YYYY-MM-DD).

Raw schema

{
  "type": "object",
  "properties": {
    "imo": {
      "type": "string",
      "description": "Vessel IMO number (exactly 7 digits) to look up."
    },
    "name": {
      "type": "string",
      "description": "Vessel name to look up (use when the IMO is unknown)."
    },
    "from": {
      "type": "string",
      "description": "Only include incidents on or after this date (YYYY-MM-DD)."
    },
    "to": {
      "type": "string",
      "description": "Only include incidents on or before this date (YYYY-MM-DD)."
    }
  },
  "additionalProperties": false
}

intel_class

Return a vessel's classification society together with its principal technical particulars: gross and net tonnage, deadweight, length overall, length between perpendiculars, beam, depth, design draft, propulsion and engine maker, plus owner/manager and next survey dates. Identify the vessel by imo or name (set fuzzy for loose name matching), or filter by owner/manager. Part of the Maritime Reports add-on.

Parameters8

imo	string	optional	Vessel IMO number (exactly 7 digits) to look up.
name	string	optional	Vessel name to look up (use when the IMO is unknown).
fuzzy	boolean	optional	Match the name loosely instead of exactly.
beneficial_owner	string	optional	Filter by beneficial owner company name.
beneficial_owner_imo	string	optional	Filter by beneficial owner company IMO number.
technical_manager	string	optional	Filter by technical manager company name.
technical_manager_imo	string	optional	Filter by technical manager company IMO number.
updated_from	string	optional	Only include records updated on or after this date (YYYY-MM-DD).

Raw schema

{
  "type": "object",
  "properties": {
    "imo": {
      "type": "string",
      "description": "Vessel IMO number (exactly 7 digits) to look up."
    },
    "name": {
      "type": "string",
      "description": "Vessel name to look up (use when the IMO is unknown)."
    },
    "fuzzy": {
      "type": "boolean",
      "description": "Match the name loosely instead of exactly."
    },
    "beneficial_owner": {
      "type": "string",
      "description": "Filter by beneficial owner company name."
    },
    "beneficial_owner_imo": {
      "type": "string",
      "description": "Filter by beneficial owner company IMO number."
    },
    "technical_manager": {
      "type": "string",
      "description": "Filter by technical manager company name."
    },
    "technical_manager_imo": {
      "type": "string",
      "description": "Filter by technical manager company IMO number."
    },
    "updated_from": {
      "type": "string",
      "description": "Only include records updated on or after this date (YYYY-MM-DD)."
    }
  },
  "additionalProperties": false
}

intel_companies

Look up a maritime company profile — owners, operators, managers and charterers — returning its full and short name, company type, registration country, operating status, contact details, and parent company. Search by the company's own IMO number (company_imo) or by name. This is a company directory, so company_imo refers to the company (not a vessel); to find the companies behind a specific ship use intel_ownership. Part of the Maritime Reports add-on.

Parameters3

company_imo	string	optional	Company IMO number (exactly 7 digits). Note this is the company's own IMO, not a vessel IMO.
name	string	optional	Company name to search for.
updated_from	string	optional	Only include records updated on or after this date (YYYY-MM-DD).

Raw schema

{
  "type": "object",
  "properties": {
    "company_imo": {
      "type": "string",
      "description": "Company IMO number (exactly 7 digits). Note this is the company's own IMO, not a vessel IMO."
    },
    "name": {
      "type": "string",
      "description": "Company name to search for."
    },
    "updated_from": {
      "type": "string",
      "description": "Only include records updated on or after this date (YYYY-MM-DD)."
    }
  },
  "additionalProperties": false
}

intel_drydock

Look up planned and past dry-dock dates, special-survey dates, and IOPP (oil-pollution) certificate dates for a vessel, along with its technical manager's contact details. Target a single vessel by imo or name, or scan a forward window across the fleet with dry_dock_from / dry_dock_to to find vessels due for drydocking in a date range. Part of the Maritime Reports add-on.

Parameters4

imo	string	optional	Vessel IMO number (exactly 7 digits) to look up.
name	string	optional	Vessel name to look up (use when the IMO is unknown).
dry_dock_from	string	optional	Only include vessels whose next dry dock falls on or after this date (YYYY-MM-DD).
dry_dock_to	string	optional	Only include vessels whose next dry dock falls on or before this date (YYYY-MM-DD).

Raw schema

{
  "type": "object",
  "properties": {
    "imo": {
      "type": "string",
      "description": "Vessel IMO number (exactly 7 digits) to look up."
    },
    "name": {
      "type": "string",
      "description": "Vessel name to look up (use when the IMO is unknown)."
    },
    "dry_dock_from": {
      "type": "string",
      "description": "Only include vessels whose next dry dock falls on or after this date (YYYY-MM-DD)."
    },
    "dry_dock_to": {
      "type": "string",
      "description": "Only include vessels whose next dry dock falls on or before this date (YYYY-MM-DD)."
    }
  },
  "additionalProperties": false
}

intel_engine

Return the main-engine specification for a vessel: engine designation (model), builder and designer, propulsion type, and maximum continuous output (MCO) with its unit and rpm. Identify the vessel by imo or name (set fuzzy for loose name matching). Part of the Maritime Reports add-on.

Parameters4

imo	string	optional	Vessel IMO number (exactly 7 digits) to look up.
name	string	optional	Vessel name to look up (use when the IMO is unknown).
fuzzy	boolean	optional	Match the name loosely instead of exactly.
updated_from	string	optional	Only include records updated on or after this date (YYYY-MM-DD).

Raw schema

{
  "type": "object",
  "properties": {
    "imo": {
      "type": "string",
      "description": "Vessel IMO number (exactly 7 digits) to look up."
    },
    "name": {
      "type": "string",
      "description": "Vessel name to look up (use when the IMO is unknown)."
    },
    "fuzzy": {
      "type": "boolean",
      "description": "Match the name loosely instead of exactly."
    },
    "updated_from": {
      "type": "string",
      "description": "Only include records updated on or after this date (YYYY-MM-DD)."
    }
  },
  "additionalProperties": false
}

intel_info

Check whether the Maritime Reports add-on is active on the connected Datalastic account, and what it offers: vessel ownership/management, classification, engine specs, Port State Control inspections, casualties, drydock schedules, sale & purchase records, company profiles, sea routes, estimated out-of-AIS positions, and bulk dataset exports. Use this when the user asks whether they have (or what is included in) the add-on, when an intel_* tool reports the add-on is missing, or after the user says they have purchased or updated their subscription.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "additionalProperties": false
}

intel_inspections

Retrieve a vessel's Port State Control (PSC) inspection record: the inspecting authority and port, the inspection type and date, whether the vessel was detained, and the number and description of any deficiencies found. Identify the vessel by imo or name, and optionally bound the period with from / to. Part of the Maritime Reports add-on.

Parameters4

imo	string	optional	Vessel IMO number (exactly 7 digits) to look up.
name	string	optional	Vessel name to look up (use when the IMO is unknown).
from	string	optional	Only include inspections on or after this date (YYYY-MM-DD).
to	string	optional	Only include inspections on or before this date (YYYY-MM-DD).

Raw schema

{
  "type": "object",
  "properties": {
    "imo": {
      "type": "string",
      "description": "Vessel IMO number (exactly 7 digits) to look up."
    },
    "name": {
      "type": "string",
      "description": "Vessel name to look up (use when the IMO is unknown)."
    },
    "from": {
      "type": "string",
      "description": "Only include inspections on or after this date (YYYY-MM-DD)."
    },
    "to": {
      "type": "string",
      "description": "Only include inspections on or before this date (YYYY-MM-DD)."
    }
  },
  "additionalProperties": false
}

intel_ownership

Reveal the commercial control behind a vessel: beneficial owner, operator, technical manager and commercial manager — each with its company IMO and country — plus the P&I club and flag. Look up one vessel by imo or name, or turn the question around and pass a company name (beneficial_owner, operator, technical_manager or commercial_manager) to list every vessel that company controls. Part of the Maritime Reports add-on.

Parameters7

imo	string	optional	Vessel IMO number (exactly 7 digits) to look up.
name	string	optional	Vessel name to look up (use when the IMO is unknown).
beneficial_owner	string	optional	Company name of the beneficial owner; returns every vessel under that owner.
operator	string	optional	Company name of the operator; returns every vessel under that operator.
technical_manager	string	optional	Company name of the technical manager; returns every vessel under that manager.
commercial_manager	string	optional	Company name of the commercial manager; returns every vessel under that manager.
updated_from	string	optional	Only include records updated on or after this date (YYYY-MM-DD).

Raw schema

{
  "type": "object",
  "properties": {
    "imo": {
      "type": "string",
      "description": "Vessel IMO number (exactly 7 digits) to look up."
    },
    "name": {
      "type": "string",
      "description": "Vessel name to look up (use when the IMO is unknown)."
    },
    "beneficial_owner": {
      "type": "string",
      "description": "Company name of the beneficial owner; returns every vessel under that owner."
    },
    "operator": {
      "type": "string",
      "description": "Company name of the operator; returns every vessel under that operator."
    },
    "technical_manager": {
      "type": "string",
      "description": "Company name of the technical manager; returns every vessel under that manager."
    },
    "commercial_manager": {
      "type": "string",
      "description": "Company name of the commercial manager; returns every vessel under that manager."
    },
    "updated_from": {
      "type": "string",
      "description": "Only include records updated on or after this date (YYYY-MM-DD)."
    }
  },
  "additionalProperties": false
}

intel_report_request

Submit an async job to export a FULL bulk dataset for one of the Maritime Reports add-on datasets (dry_dock_dates, casualty, inspections, sales_purchase_demolitions, ownership, class_society, engine, companies). This returns the ENTIRE dataset (all records), not one vessel — for a single vessel use the matching lookup tool instead (e.g. intel_ownership, intel_inspections). Like all reports it is asynchronous: this returns a report_id and a _PENDING_ status without waiting; submit ONCE, then poll report_status with that report_id until _DONE_, which yields a result_url to hand to the user to download. The server never downloads the file itself. Part of the Maritime Reports add-on.

Parameters1

report_type

string

required

Which bulk dataset report to generate. One of: dry_dock_dates, casualty, inspections, sales_purchase_demolitions, ownership, class_society, engine, companies.

Raw schema

{
  "type": "object",
  "properties": {
    "report_type": {
      "type": "string",
      "description": "Which bulk dataset report to generate. One of: dry_dock_dates, casualty, inspections, sales_purchase_demolitions, ownership, class_society, engine, companies."
    }
  },
  "required": [
    "report_type"
  ],
  "additionalProperties": false
}

intel_spd

Retrieve ship sale-and-purchase transactions for a vessel: second-hand sales, newbuilding deliveries and demolition (scrap) sales, including seller, buyer, reported price, price per lightweight ton, and demolition destination. Useful for asset valuation and market tracking. Identify the vessel by imo or name, and optionally bound the period with from / to. Part of the Maritime Reports add-on.

Parameters4

imo	string	optional	Vessel IMO number (exactly 7 digits) to look up.
name	string	optional	Vessel name to look up (use when the IMO is unknown).
from	string	optional	Only include transactions reported on or after this date (YYYY-MM-DD).
to	string	optional	Only include transactions reported on or before this date (YYYY-MM-DD).

Raw schema

{
  "type": "object",
  "properties": {
    "imo": {
      "type": "string",
      "description": "Vessel IMO number (exactly 7 digits) to look up."
    },
    "name": {
      "type": "string",
      "description": "Vessel name to look up (use when the IMO is unknown)."
    },
    "from": {
      "type": "string",
      "description": "Only include transactions reported on or after this date (YYYY-MM-DD)."
    },
    "to": {
      "type": "string",
      "description": "Only include transactions reported on or before this date (YYYY-MM-DD)."
    }
  },
  "additionalProperties": false
}

report_list

List the caller's recent async report jobs with their statuses (and result_url once _DONE_). Use this to recover a report_id or see which reports have finished — for example if a report was submitted earlier and its id was lost.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "additionalProperties": false
}

report_request

Submit an async report job. Reports are generated in the background and can take a while (seconds to many minutes), so this returns a report_id and an initial status (_PENDING_) — it does NOT wait. Submit ONCE, then poll report_status with the returned report_id until _DONE_, which yields a result_url. Do not resubmit while a job is running. When done, give the user the result_url to download; the server never downloads report files itself. Supported report_type values: - request_usage: a FREE log of your account's API usage (endpoint, credits, timestamp); optional from/to (<=31 days), default last month. - vessel_list: the full vessel database (no other parameters). - port_list: the full ports database (no other parameters). - inradius_history: all vessels that passed through an area in a time window; REQUIRES lat, lon, radius (<=50 NM), from and to (<=7 days apart). Note: vessel_list, port_list and inradius_history consume API credits (vessel_list and inradius_history can be substantial) — it's good to tell the user before submitting. For the add-on bulk datasets (ownership, inspections, etc.) use intel_report_request instead.

Parameters6

report_type	string	required	Which report to generate: request_usage, vessel_list, port_list, or inradius_history.
from	string	optional	Start date YYYY-MM-DD. Optional for request_usage; required for inradius_history.
to	string	optional	End date YYYY-MM-DD. Optional for request_usage (<=31 days after from); required for inradius_history (<=7 days after from).
lat	null \| number	optional	Center latitude. Required for inradius_history.
lon	null \| number	optional	Center longitude. Required for inradius_history.
radius	null \| number	optional	Radius in nautical miles, max 50. Required for inradius_history.

Raw schema

{
  "type": "object",
  "properties": {
    "report_type": {
      "type": "string",
      "description": "Which report to generate: request_usage, vessel_list, port_list, or inradius_history."
    },
    "from": {
      "type": "string",
      "description": "Start date YYYY-MM-DD. Optional for request_usage; required for inradius_history."
    },
    "to": {
      "type": "string",
      "description": "End date YYYY-MM-DD. Optional for request_usage (<=31 days after from); required for inradius_history (<=7 days after from)."
    },
    "lat": {
      "type": [
        "null",
        "number"
      ],
      "description": "Center latitude. Required for inradius_history."
    },
    "lon": {
      "type": [
        "null",
        "number"
      ],
      "description": "Center longitude. Required for inradius_history."
    },
    "radius": {
      "type": [
        "null",
        "number"
      ],
      "description": "Radius in nautical miles, max 50. Required for inradius_history."
    }
  },
  "required": [
    "report_type"
  ],
  "additionalProperties": false
}

report_status

Check an async report job by report_id (from report_request or report_list). Returns its status: _PENDING_ or _IN_PROGRESS_ (still generating — wait a bit and check again) or _DONE_. When _DONE_, result_url is a download link for the result ZIP; hand it to the user. Links are time-limited — if one has expired, run report_status again for a fresh link. The server never downloads the file itself.

Parameters1

report_id

string

required

The report_id returned by report_request (or seen in report_list).

Raw schema

{
  "type": "object",
  "properties": {
    "report_id": {
      "type": "string",
      "description": "The report_id returned by report_request (or seen in report_list)."
    }
  },
  "required": [
    "report_id"
  ],
  "additionalProperties": false
}

sea_route

Calculate a schematic sea route between two points and return it as GeoJSON (a LineString of waypoints) with the total distance in kilometres and nautical miles. Specify the origin and destination each as either coordinates (lat+lon), a port UUID, or a port UN/LOCODE. ⚠️ This is a SCHEMATIC sea route, not a navigable one. It does not account for actual navigation, hazards, traffic separation, drafts or local rules — do NOT use it for real-world sailing. Use it for estimating distance and travel time, visualizing the approximate path/shape, and similar analysis. Part of the Maritime Reports add-on.

Parameters8

lat_from	null \| number	optional	Origin latitude (use together with lon_from).
lon_from	null \| number	optional	Origin longitude (use together with lat_from).
port_uuid_from	string	optional	Origin port UUID.
port_unlocode_from	string	optional	Origin port UN/LOCODE (5 alphanumeric, case-insensitive).
lat_to	null \| number	optional	Destination latitude (use together with lon_to).
lon_to	null \| number	optional	Destination longitude (use together with lat_to).
port_uuid_to	string	optional	Destination port UUID.
port_unlocode_to	string	optional	Destination port UN/LOCODE (5 alphanumeric, case-insensitive).

Raw schema

{
  "type": "object",
  "properties": {
    "lat_from": {
      "type": [
        "null",
        "number"
      ],
      "description": "Origin latitude (use together with lon_from)."
    },
    "lon_from": {
      "type": [
        "null",
        "number"
      ],
      "description": "Origin longitude (use together with lat_from)."
    },
    "port_uuid_from": {
      "type": "string",
      "description": "Origin port UUID."
    },
    "port_unlocode_from": {
      "type": "string",
      "description": "Origin port UN/LOCODE (5 alphanumeric, case-insensitive)."
    },
    "lat_to": {
      "type": [
        "null",
        "number"
      ],
      "description": "Destination latitude (use together with lon_to)."
    },
    "lon_to": {
      "type": [
        "null",
        "number"
      ],
      "description": "Destination longitude (use together with lat_to)."
    },
    "port_uuid_to": {
      "type": "string",
      "description": "Destination port UUID."
    },
    "port_unlocode_to": {
      "type": "string",
      "description": "Destination port UN/LOCODE (5 alphanumeric, case-insensitive)."
    }
  },
  "additionalProperties": false
}

README.md8 KBView on GitHub

Datalastic MCP Server

Official Model Context Protocol (MCP) server for Datalastic — real-time vessel tracking, port data, maritime weather, and maritime intelligence for any MCP-compatible AI client.

Overview

The Datalastic MCP server exposes 25 tools across six categories:

Live vessel positions — track ships in real time by MMSI, IMO, or name
Vessel registry — specs, dimensions, flag, and tonnage for 750,000+ vessels
Port data — global port and terminal directory with UN/LOCODEs
Area search — all vessels currently within a radius of any point or port
Maritime weather — wave, swell, and sea conditions merged with atmospheric weather, with 7-day forecasts at any coordinates, port, or vessel
Maritime intelligence (Maritime Reports add-on) — ownership, inspections, casualties, dry dock, engine specs, sale & purchase transactions

The server runs at mcp.datalastic.com — no local installation required.

Getting Started

No API key needed. Just add https://mcp.datalastic.com/mcp as the server URL in your client with no headers or credentials. When you connect, your client will automatically open a browser window to sign in with your Datalastic account. Once you approve, you're connected — the client handles everything else.

To disconnect, use the disconnect option in your MCP client or revoke access from your Datalastic account settings.

API key

Sign up at datalastic.com/pricing and subscribe to a plan. Your API key is delivered by email and visible in your account dashboard.

For clients that support custom request headers in their config file, use the examples in the Client Configuration section below. For Claude Code, use the CLI command instead.

Client Configuration

Claude Code

Run this command to add the server with your API key:

code

claude mcp add --scope user --transport http datalastic https://mcp.datalastic.com/mcp --header "X-Api-Key: YOUR_API_KEY"

For Claude Desktop, use OAuth (sign in with your Datalastic account above) — custom header authentication via config file is not yet supported.

Cursor

Edit ~/.cursor/mcp.json:

json

{
  "mcpServers": {
    "datalastic": {
      "type": "http",
      "url": "https://mcp.datalastic.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY"
      }
    }
  }
}

VS Code (GitHub Copilot)

Edit .vscode/mcp.json in your workspace, or your user-level mcp.json:

json

{
  "servers": {
    "datalastic": {
      "type": "http",
      "url": "https://mcp.datalastic.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY"
      }
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

json

{
  "mcpServers": {
    "datalastic": {
      "type": "http",
      "url": "https://mcp.datalastic.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY"
      }
    }
  }
}

Gemini CLI

Edit ~/.gemini/settings.json:

json

{
  "mcpServers": {
    "datalastic": {
      "httpUrl": "https://mcp.datalastic.com/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY"
      }
    }
  }
}

Any Streamable HTTP client

code

URL:    https://mcp.datalastic.com/mcp
Header: X-Api-Key: YOUR_API_KEY

Tools

All 25 tools are always listed in your client. The Maritime Intelligence tools require the Maritime Reports add-on; everything else is available on every plan.

Vessel Tracking

get_vessel - Live position, speed, heading, and navigation status for a single vessel
get_vessel_pro - Like get_vessel plus recognized destination port, ETA, actual departure time, and draught
get_vessel_info - Static specifications: dimensions, tonnage, cargo capacity, year built, flag, callsign
find_vessels - Search the registry by name, type, flag, tonnage, or dimensions
get_vessels_bulk - Live positions for up to 100 vessels in one call
get_vessel_history - Historical AIS track for a vessel (data available since 2021-08-10)
get_vessels_in_radius - All vessels currently within a radius (max 50 NM) of a point, port, or vessel

Choosing the right vessel tool: start with get_vessel for a live position. Use get_vessel_pro only when you need the destination port, ETA, or draught.

Ports

find_ports - Search the port registry by name, UN/LOCODE, country, type, or coordinates
get_port - Full port detail including terminals, operators, addresses, and coordinates

Maritime Weather

get_weather - One complete weather picture: marine conditions (waves, swell, currents, sea surface temperature) merged with atmospheric conditions (wind, temperature, visibility, pressure). Works at fixed coordinates, at a port, or around a vessel, resolving to the ship's last known position. Returns current conditions plus 7-day daily and hourly forecasts

Maritime Intelligence (Maritime Reports add-on)

intel_ownership - Beneficial owner, operator, technical and commercial manager, P&I club
intel_inspections - Port State Control inspection records — detentions and deficiencies
intel_casualties - Recorded incidents: groundings, collisions, fires, machinery failures
intel_drydock - Next dry-dock date, special-survey date, and IOPP certificate expiry
intel_class - Classification society, principal dimensions, and next survey dates
intel_engine - Main engine model, builder, propulsion type, and maximum continuous output
intel_spd - Sale-and-purchase and demolition transactions — buyer, seller, reported price
intel_companies - Maritime company profiles: owners, operators, managers, and contact details
sea_route - Schematic sea route and distance in km / NM between two ports or coordinates. For distance estimation and visualization — not for real-world navigation.
estimated_vessel_position - Estimated current position for vessels out of terrestrial AIS range (open ocean)
intel_report_request - Submit a full bulk export of any Maritime Reports dataset
intel_info - Your Maritime Reports add-on status, what the add-on includes, and how to enable it (available on all plans)

Don't have the add-on? Calling a Maritime Intelligence tool without the Maritime Reports add-on returns a message explaining that the add-on is required — intel_info shows your status and how to enable it. Upgrades take effect immediately in the same session, no reconnect needed.

Bulk Reports (async)

report_request - Submit an async export: vessel_list, port_list, inradius_history, or request_usage
report_status - Poll a report job; returns a download URL when complete
report_list - List your recent report jobs and statuses

Reports are generated asynchronously and can take minutes. The server returns a result_url to download — it never fetches the file itself. Download links are signed URLs valid for 6 hours; checking the report status again issues a fresh link at any time, free, without regenerating the export. Some exports (full vessel list, area history) can be large and consume API credits.

Example Prompts

code

Where is the MSC Oscar right now and what is its destination?

Show me all tankers within 20 nautical miles of Rotterdam.

What is the weather forecast at the Port of Singapore for the next 7 days?

What are the wave and wind conditions around the Ever Given right now?

Who is the beneficial owner of IMO 9839179?

Get the Port State Control inspection history for the Ever Given.

What is the sea route distance from Shanghai to Los Angeles?

Find all bulk carriers built after 2018 flagged in the Marshall Islands.

Which vessels does Maersk operate?

Show me all vessels with dry docks scheduled in the next 30 days.

What incidents has this tanker been involved in over the past 5 years?

Install

Tools (25)

estimated_vessel_positionfind_portsfind_vesselsget_portget_vesselget_vessel_historyget_vessel_infoget_vessel_pro

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.datalastic.com/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "vessel-tracking": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.datalastic.com/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

Datalastic Vessel Tracking MCP Server (com.datalastic/vessel-tracking)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

estimated_vessel_position

find_ports

find_vessels

get_port

get_vessel

get_vessel_history

get_vessel_info

get_vessel_pro

get_vessels_bulk

get_vessels_in_radius

get_weather

intel_casualties

intel_class

intel_companies

intel_drydock

intel_engine

intel_info

intel_inspections

intel_ownership

intel_report_request

intel_spd

report_list

report_request

report_status

sea_route

Datalastic MCP Server

Overview

Getting Started

Sign in with your Datalastic account

API key

Client Configuration

Claude Code

Cursor

VS Code (GitHub Copilot)

Windsurf

Gemini CLI

Any Streamable HTTP client

Tools

Example Prompts

Links

Install

Remote endpoint

Related servers