Everything here was measured by our prober or read from a registry. Nothing is self-reported.
30-day availability1/1 checks ok
30 days agotoday
Endpoints
https://mcp.datalastic.com/mcpmcp streamable http · checked on a schedule
Registry facts
Not distributed through a package registry we index.
when
check
result
http
latency
detail
1 h ago
mcp initialize
ok
200
28 ms
server datalastic-mcp 0.1.0 · protocol 2025-06-18 · 25 tools
Tools observed via MCP handshake
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
Declared by sources
What the publisher says
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
kind ← Official MCP Registry
name ← Official MCP Registry
repoUrl ← Official MCP Registry
summary ← Official MCP Registry
version ← Official MCP Registry
description ← Official MCP Registry
publisherName ← Official MCP Registry
Derived by Wellknown
Capabilities
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
4 h ago · declared · summary → "Vessel tracking for 750,000+ ships, with ownership, inspections, port records, routes, and more."
4 h ago · declared · description → "Vessel tracking for 750,000+ ships, with ownership, inspections, port records, routes, and more."
4 h ago · declared · publisherName → "com.datalastic"
4 h ago · declared · repoUrl → "https://github.com/datalastic/mcp-server-datalastic"
4 h ago · declared · version → "1.0.0"
4 h ago · declared · protocols → ["mcp"]
— 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