MCP servercom.datalastic/vessel-tracking
Vessel tracking for 750,000+ ships, with ownership, inspections, port records, routes, and more.
Overview
Score?
UNRATED 0.824
of what a free look can see, on 32 looks
Looks
36
last 9 hr ago
Tools
25
More info
URL
mcp.datalastic.com/mcp
streamable-http
Says it is
datalastic-mcp 0.1.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.824 · highest on record 0.8561
Toolsfrom sha256:1b43306ca1…e859f0
| Tool | Schema |
|---|---|
| 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 calc |
input · output |
| 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, classif |
input · output |
| 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 s |
input · output |
| 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, coordi |
input · output |
| 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, |
input · output |
| 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 rang |
input · output |
| 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, |
input · output |
| 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 |
input · output |
| 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 th |
input · output |
| 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 coordina |
input · output |
| 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 |
input · output |
| 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 de |
input · output |
| 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, |
input · output |
| 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 d |
input · output |
| 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 |
input · output |
| 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. Ide |
input · output |
| 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 C |
input · output |
| 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 |
input · output |
| 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 |
input · output |
| 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, cla |
input · output |
| 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 pe |
input · output |
| 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 reco |
input · output |
| 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_) — |
input · output |
| 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 _F |
input · output |
| 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 |
input · output |
Verify it yourself
npx teppi-check https://mcp.datalastic.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ25Y5N7F53KYJ8B6JVNYK