Datalastic Vessel Tracking & Maritime Intelligence is a remote MCP server that gives an AI agent 25 tools, among them estimated_vessel_position, find_ports, find_vessels. It answers at https://mcp.datalastic.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 18 October 2026, succeeded.
Vessel tracking for 750,000+ ships, with ownership, inspections, port records, routes, and more.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 p Inputs: mmsi, imo, uuid |
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 n Inputs: name, uuid, fuzzy, port_type, country_iso, unlocode |
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 bui Inputs: name, fuzzy, type, type_specific, country_iso, gross_tonnage_min |
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 Inputs: uuid, unlocode |
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 d Inputs: mmsi, imo, uuid |
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 (YYY Inputs: mmsi, imo, uuid, days, from, to |
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, deadwei Inputs: mmsi, imo, uuid |
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 ori Inputs: mmsi, imo, uuid |
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 Inputs: mmsi, imo, uuid |
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 cen Inputs: lat, lon, port_unlocode, port_uuid, mmsi, imo |
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, Inputs: lat, lon, mmsi, imo, uuid, port_unlocode |
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. Identif Inputs: imo, name, from, to |
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 Inputs: imo, name, fuzzy, beneficial_owner, beneficial_owner_imo, technical_manager |
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 Inputs: company_imo, name, updated_from |
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 acro Inputs: imo, name, dry_dock_from, dry_dock_to |
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 ma Inputs: imo, name, fuzzy, updated_from |
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 & pu |
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 Inputs: imo, name, from, to |
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 questio Inputs: imo, name, beneficial_owner, operator, technical_manager, commercial_manager |
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 data Inputs: report_type |
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 as Inputs: imo, name, from, to |
report_list | List the caller's recent async report jobs with their statuses — result_url on the ones that are _DONE_, and message explaining the cause on any that are _FAILED_. Use this to recover a report_id, see which reports have finished, or find ou |
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 Inputs: report_type, from, to, lat, lon, radius |
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 and check again), _DONE_, or _FAILED_. When _DONE_, result_url is a download link for the r Inputs: report_id |
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 por Inputs: lat_from, lon_from, port_uuid_from, port_unlocode_from, lat_to, lon_to |
Every block below points at https://mcp.datalastic.com/mcp. Pick your client and copy.
claude mcp add --transport http datalastic-vessel-tracking-marit https://mcp.datalastic.com/mcp
{
"mcpServers": {
"datalastic-vessel-tracking-marit": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.datalastic.com/mcp"]
}
}
}{
"mcpServers": {
"datalastic-vessel-tracking-marit": {
"url": "https://mcp.datalastic.com/mcp"
}
}
}{
"servers": {
"datalastic-vessel-tracking-marit": {
"type": "http",
"url": "https://mcp.datalastic.com/mcp"
}
}
}{
"context_servers": {
"datalastic-vessel-tracking-marit": {
"url": "https://mcp.datalastic.com/mcp"
}
}
}{
"mcpServers": {
"datalastic-vessel-tracking-marit": {
"serverUrl": "https://mcp.datalastic.com/mcp"
}
}
}{
"mcpServers": {
"datalastic-vessel-tracking-marit": {
"url": "https://mcp.datalastic.com/mcp"
}
}
}name: Datalastic Vessel Tracking & Maritime Intelligence
version: 0.0.1
schema: v1
mcpServers:
- name: Datalastic Vessel Tracking & Maritime Intelligence
type: streamable-http
url: https://mcp.datalastic.com/mcp{
"mcpServers": {
"datalastic-vessel-tracking-marit": {
"httpUrl": "https://mcp.datalastic.com/mcp"
}
}
}{
"mcpServers": {
"datalastic-vessel-tracking-marit": {
"type": "http",
"url": "https://mcp.datalastic.com/mcp"
}
}
}{
"mcpServers": {
"datalastic-vessel-tracking-marit": {
"url": "https://mcp.datalastic.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.datalastic.com%2Fmcp&type=streamable_http&id=datalastic-vessel-tracking-marit&name=Datalastic%20Vessel%20Tracking%20%26%20Maritime%20Intelligence
It answered our last check on 18 October 2026 in 94 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by datalastic.com and served from mcp.datalastic.com, the vendor's own domain: https://mcp.datalastic.com/mcp.
25, as returned by the server's own tools/list on 10 September 2026: estimated_vessel_position, find_ports, find_vessels, get_port, get_vessel, get_vessel_history, get_vessel_info, get_vessel_pro, and 17 more.
It answered our last check on 18 October 2026 in 94 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.datalastic.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.datalastic. Endpoint host: mcp.datalastic.com. ARD identifier: urn:air:com.datalastic:mcp:vessel-tracking.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.