MCP server

Datalastic Vessel Tracking & Maritime Intelligence Official

com.datalastic/vessel-tracking

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

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

Source

At a glance

Type

MCP server

Publisher

datalastic.com (verified by the MCP Registry)

Status

Working at last check

Tools

25

Token cost

About 8,920 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http vessel-tracking https://mcp.datalastic.com/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.vessel-tracking]
url = "https://mcp.datalastic.com/mcp"

Gemini CLI

{"mcpServers":{"vessel-tracking":{"httpUrl":"https://mcp.datalastic.com/mcp"}}}

Cursor

{"mcpServers":{"vessel-tracking":{"url":"https://mcp.datalastic.com/mcp"}}}

VS Code

{"servers":{"vessel-tracking":{"type":"http","url":"https://mcp.datalastic.com/mcp"}}}

Antigravity

agy mcp add vessel-tracking https://mcp.datalastic.com/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"vessel-tracking","server_url":"https://mcp.datalastic.com/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"vessel-tracking","server_url":"https://mcp.datalastic.com/mcp"}

Tools

• estimated_vessel_position ~462 tokens
  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 obse
• find_ports ~434 tokens
  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 mat
• find_vessels ~674 tokens
  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
• get_port ~218 tokens
  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 b
• get_vessel ~283 tokens
  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
• get_vessel_history ~367 tokens
  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 availab
• get_vessel_info ~283 tokens
  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, fl
• get_vessel_pro ~371 tokens
  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 (AT
• get_vessels_bulk ~258 tokens
  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). U
• get_vessels_in_radius ~687 tokens
  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_specifi
• get_weather ~481 tokens
  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,
• intel_casualties ~245 tokens
  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
• intel_class ~374 tokens
  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 o
• intel_companies ~258 tokens
  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
• intel_drydock ~269 tokens
  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 vessel
• intel_engine ~225 tokens
  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.
• intel_info ~187 tokens
  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-
• intel_inspections ~243 tokens
  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 /
• intel_ownership ~388 tokens
  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
• intel_report_request ~380 tokens
  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
• intel_spd ~262 tokens
  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 im
• report_list ~135 tokens
  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 out why one failed — for example if a report was submitted ear
• report_request ~645 tokens
  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_u
• report_status ~364 tokens
  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 result ZIP; hand it to the user. Links are time-limited — if
• sea_route ~427 tokens
  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 rout

Browse

• Forms and surveys
• Weather

Related MCP servers

• Datalastic
  Datalastic MCP — live AIS vessel positions (datalastic.com)
• Rootz Maritime
  Signed global shipping & commodity data: oil, LNG, grain, sanctions, fleet, emissions.
• Agenda Intelligence MD
  Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs.
• Imf Portwatch
  IMF PortWatch MCP — global maritime trade & chokepoint signals (free, no auth)
• Vessel Tracking
  Vessel Tracking — live worldwide ship positions from AIS.
• Digitraffic Ais
  Digitraffic AIS MCP — live vessel positions in Finnish and Baltic Sea waters.
• AIS Trail
  Live AIS ship positions, vessel history, port calls and events, plus sanctions flags. Read-only.
• Open Waters AIS
  Live AIS vessel positions by MMSI, name, area, or radius, plus coverage. No sign-in, no key.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/com.datalastic/vessel-tracking.svg)](https://aptlynx.net/servers/com.datalastic/vessel-tracking)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents