com.datalastic/vessel-tracking

up checked 2026-11-11T04:38:58.444Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Datalastic Vessel Tracking & Maritime Intelligence

Publisher-provided description

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

Summary by lookupd

Tracks ships and ports worldwide, retrieving positions, histories, ownership, inspections, routes and marine weather for maritime analysis.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add vessel-tracking --url https://mcp.datalastic.com/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (25 tools)

Publisher-provided text

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.
find_ports Search the port registry and return matching ports (identity, country, UN/LOCODE, classification, coordinates, maritime area). Search by name (optionally fuzzy)
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. Return
get_port Return detailed information for a single port — identity, country, UN/LOCODE, classification, coordinates, maritime area, and the list of terminals (name, opera
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. Includ
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. S
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 dimension
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
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
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 w
get_weather Return weather for one location: marine conditions (wave height/direction/period, swell, sea-surface temperature, ocean currents, sea level, …) plus general atm
intel_casualties Retrieve a vessel's recorded maritime incidents — groundings, collisions, fires, machinery breakdowns, detentions and similar events — each with a date, categor
intel_class Return a vessel's classification society together with its principal technical particulars: gross and net tonnage, deadweight, length overall, length between pe
intel_companies Look up a maritime company profile — owners, operators, managers and charterers — returning its full and short name, company type, registration country, operati
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 conta
intel_engine Return the main-engine specification for a vessel: engine designation (model), builder and designer, propulsion type, and maximum continuous output (MCO) with i
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
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
intel_ownership Reveal the commercial control behind a vessel: beneficial owner, operator, technical manager and commercial manager — each with its company IMO and country — pl
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_demolit
intel_spd Retrieve ship sale-and-purchase transactions for a vessel: second-hand sales, newbuilding deliveries and demolition (scrap) sales, including seller, buyer, repo
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 _FAILE
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 s
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 a
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

Details

Version: 1.0.0
Transports: streamable-http
Uptime (7 days): 100%
Median latency: 1069 ms
First indexed: 2026-11-01T08:53:37.475Z
Last seen in registry: 2026-11-01T08:53:37.475Z
Repository: https://github.com/datalastic/mcp-server-datalastic

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/com.datalastic/vessel-tracking.svg)](https://lookupd.com/servers/com.datalastic/vessel-tracking)

62092 servers
Last crawl: 2026-11-11T17:17:22.074Z
API base: https://api.lookupd.com
MCP URL: https://api.lookupd.com/mcp