Datalastic Vessel Tracking & Maritime Intelligence

com.datalastic由 datalastic.com 发布官方发布者v1.0.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行位置与生活数据与分析

概览

AI 生成的概览

Datalastic 托管的 MCP 服务器,为 75 万艘以上船舶提供实时船舶追踪、港口数据、海事天气与海事情报。

可以做什么
查询单船实时位置、航速与航行状态,批量位置、以点/港口/船舶为中心的区域扫描,以及 2021-08-10 以来的历史 AIS 轨迹;估算超出陆基 AIS 范围的船舶位置,并计算示意性海上航线及公里/海里距离。按名称、类型、船旗、吨位或尺寸检索船舶登记库,读取尺寸、吨位、建造年份、呼号等静态参数。检索港口登记库并查看港口详情,包括码头、运营方与坐标。在坐标、港口或船舶处获取海洋与大气天气,含 7 天逐日与逐小时预报。若开通 Maritime Reports 附加包,还可查询所有权、港口国检查、事故、干船坞、船级社、主机规格、买卖与拆解交易及公司档案,并提交异步批量导出。
适用场景
需要航运或海事答案时使用:某船在哪里、港口附近有哪些船、海上天气与海况、港口与码头信息,或用于尽职调查与风险评估的所有权、检查、事故、干船坞和买卖记录。
运行要求
远程 streamable HTTP 端点,无需本地安装。可通过 Datalastic 账户 OAuth 登录,或使用付费套餐提供的 X-Api-Key 请求头认证。海事情报工具需开通 Maritime Reports 附加包,intel_info 可查看是否已启用。
安装前请注意
X-Api-Key 属于机密,勿放入共享配置。批量导出和部分报告会消耗 API 额度,大型导出可能费用较高。报告下载链接为限时签名 URL。位置仅来自陆基 AIS,远洋可能过时;估算位置与海上航线仅为示意,不可用于实际导航。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Datalastic Vessel Tracking & Maritime Intelligence,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.datalastic%2Fvessel-tracking/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

Datalastic MCP Server

Official Model Context Protocol (MCP) server for Datalastic — real-time vessel tracking, port data, maritime weather, and maritime intelligence for any MCP-compatible AI client.

[License: MIT] [MCP Badge]

Overview

The Datalastic MCP server exposes 25 tools across six categories:

  • Live vessel positions — track ships in real time by MMSI, IMO, or name
  • Vessel registry — specs, dimensions, flag, and tonnage for 750,000+ vessels
  • Port data — global port and terminal directory with UN/LOCODEs
  • Area search — all vessels currently within a radius of any point or port
  • Maritime weather — wave, swell, and sea conditions merged with atmospheric weather, with 7-day forecasts at any coordinates, port, or vessel
  • Maritime intelligence (Maritime Reports add-on) — ownership, inspections, casualties, dry dock, engine specs, sale & purchase transactions

The server runs at mcp.datalastic.com — no local installation required.


Getting Started

Sign in with your Datalastic account

No API key needed. Just add https://mcp.datalastic.com/mcp as the server URL in your client with no headers or credentials. When you connect, your client will automatically open a browser window to sign in with your Datalastic account. Once you approve, you're connected — the client handles everything else.

To disconnect, use the disconnect option in your MCP client or revoke access from your Datalastic account settings.

API key

Sign up at datalastic.com/pricing and subscribe to a plan. Your API key is delivered by email and visible in your account dashboard.

For clients that support custom request headers in their config file, use the examples in the Client Configuration section below. For Claude Code, use the CLI command instead.


Client Configuration

Claude Code

Run this command to add the server with your API key:

claude mcp add --scope user --transport http datalastic https://mcp.datalastic.com/mcp --header "X-Api-Key: YOUR_API_KEY"

For Claude Desktop, use OAuth (sign in with your Datalastic account above) — custom header authentication via config file is not yet supported.

Cursor

Edit ~/.cursor/mcp.json:

json
{  "mcpServers": {    "datalastic": {      "type": "http",      "url": "https://mcp.datalastic.com/mcp",      "headers": {        "X-Api-Key": "YOUR_API_KEY"      }    }  }}

VS Code (GitHub Copilot)

Edit .vscode/mcp.json in your workspace, or your user-level mcp.json:

json
{  "servers": {    "datalastic": {      "type": "http",      "url": "https://mcp.datalastic.com/mcp",      "headers": {        "X-Api-Key": "YOUR_API_KEY"      }    }  }}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "datalastic": {      "type": "http",      "url": "https://mcp.datalastic.com/mcp",      "headers": {        "X-Api-Key": "YOUR_API_KEY"      }    }  }}

Gemini CLI

Edit ~/.gemini/settings.json:

json
{  "mcpServers": {    "datalastic": {      "httpUrl": "https://mcp.datalastic.com/mcp",      "headers": {        "X-Api-Key": "YOUR_API_KEY"      }    }  }}

Any Streamable HTTP client

URL:    https://mcp.datalastic.com/mcpHeader: X-Api-Key: YOUR_API_KEY

Tools

All 25 tools are always listed in your client. The Maritime Intelligence tools require the Maritime Reports add-on; everything else is available on every plan.

Vessel Tracking

  • get_vessel - Live position, speed, heading, and navigation status for a single vessel
  • get_vessel_pro - Like get_vessel plus recognized destination port, ETA, actual departure time, and draught
  • get_vessel_info - Static specifications: dimensions, tonnage, cargo capacity, year built, flag, callsign
  • find_vessels - Search the registry by name, type, flag, tonnage, or dimensions
  • get_vessels_bulk - Live positions for up to 100 vessels in one call
  • get_vessel_history - Historical AIS track for a vessel (data available since 2021-08-10)
  • get_vessels_in_radius - All vessels currently within a radius (max 50 NM) of a point, port, or vessel

Choosing the right vessel tool: start with get_vessel for a live position. Use get_vessel_pro only when you need the destination port, ETA, or draught.

Ports

  • find_ports - Search the port registry by name, UN/LOCODE, country, type, or coordinates
  • get_port - Full port detail including terminals, operators, addresses, and coordinates

Maritime Weather

  • get_weather - One complete weather picture: marine conditions (waves, swell, currents, sea surface temperature) merged with atmospheric conditions (wind, temperature, visibility, pressure). Works at fixed coordinates, at a port, or around a vessel, resolving to the ship's last known position. Returns current conditions plus 7-day daily and hourly forecasts

Maritime Intelligence (Maritime Reports add-on)

  • intel_ownership - Beneficial owner, operator, technical and commercial manager, P&I club
  • intel_inspections - Port State Control inspection records — detentions and deficiencies
  • intel_casualties - Recorded incidents: groundings, collisions, fires, machinery failures
  • intel_drydock - Next dry-dock date, special-survey date, and IOPP certificate expiry
  • intel_class - Classification society, principal dimensions, and next survey dates
  • intel_engine - Main engine model, builder, propulsion type, and maximum continuous output
  • intel_spd - Sale-and-purchase and demolition transactions — buyer, seller, reported price
  • intel_companies - Maritime company profiles: owners, operators, managers, and contact details
  • sea_route - Schematic sea route and distance in km / NM between two ports or coordinates. For distance estimation and visualization — not for real-world navigation.
  • estimated_vessel_position - Estimated current position for vessels out of terrestrial AIS range (open ocean)
  • intel_report_request - Submit a full bulk export of any Maritime Reports dataset
  • intel_info - Your Maritime Reports add-on status, what the add-on includes, and how to enable it (available on all plans)

Don't have the add-on? Calling a Maritime Intelligence tool without the Maritime Reports add-on returns a message explaining that the add-on is required — intel_info shows your status and how to enable it. Upgrades take effect immediately in the same session, no reconnect needed.

Bulk Reports (async)

  • report_request - Submit an async export: vessel_list, port_list, inradius_history, or request_usage
  • report_status - Poll a report job; returns a download URL when complete
  • report_list - List your recent report jobs and statuses

Reports are generated asynchronously and can take minutes. The server returns a result_url to download — it never fetches the file itself. Download links are signed URLs valid for 6 hours; checking the report status again issues a fresh link at any time, free, without regenerating the export. Some exports (full vessel list, area history) can be large and consume API credits.


Example Prompts

Where is the MSC Oscar right now and what is its destination?
Show me all tankers within 20 nautical miles of Rotterdam.
What is the weather forecast at the Port of Singapore for the next 7 days?
What are the wave and wind conditions around the Ever Given right now?
Who is the beneficial owner of IMO 9839179?
Get the Port State Control inspection history for the Ever Given.
What is the sea route distance from Shanghai to Los Angeles?
Find all bulk carriers built after 2018 flagged in the Marshall Islands.
Which vessels does Maersk operate?
Show me all vessels with dry docks scheduled in the next 30 days.
What incidents has this tanker been involved in over the past 5 years?

Links

来源:README.md,提交 69ce98b

工具

25

estimated_vessel_position

Estimate a vessel's current position (SAT-E)

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 observed position. Tool selection — use this LAST: prefer get_vessel for a live position (cheapest); prefer get_vessel_pro when the user wants the ETA or recognized destination. Only reach for this tool when BOTH hold: (1) a prior get_vessel/get_vessel_pro lookup shows the last known position is old, and (2) the vessel has a destination and an ETA. It is the heaviest call (it builds a route) and adds nothing when get_vessel already returns a recent position. Because it is an estimate, OFFER it to the user first rather than calling it silently, and when you present the result make clear it is an estimated position, not a real fix. If estimated_position equals the last known lat/lon, the system could not extrapolate (the position is recent, or the ETA is missing/outdated) — say so instead of implying movement.

输入参数imommsiuuid

find_ports

Search for 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 nautical miles). Always returns a list, even for a single match. Use this to discover ports or resolve a name to a UN/LOCODE/uuid; for full detail on one known port (including terminals) use get_port.

输入参数latlonnameuuidfuzzyradiusunlocodeport_typecountry_iso

find_vessels

Find vessels (registry search)

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 live position. Provide at least one search criterion; use the response's next token via the next argument to page. Credits: 1 per vessel found. For a vessel's live position use get_vessel; for vessels currently in an area use get_vessels_in_radius.

输入参数namenexttypefuzzylength_maxlength_minbreadth_maxbreadth_mincountry_isotype_specificdeadweight_maxdeadweight_min另有 5 个

get_port

Get one port with its terminals

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 by name or location, or when you don't have an exact identifier, use find_ports first.

输入参数uuidunlocode

get_vessel

Get vessel position

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. For the recognized destination or origin port (name + UNLOCODE), actual departure time (ATD), a reliable estimated time of arrival (ETA), or draught, use get_vessel_pro instead.

输入参数imommsiuuid

get_vessel_history

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 (YYYY-MM-DD, 'to' at most 30 days after 'from'). Data is available since 2021-08-10; only position changes are stored, so stationary periods may have gaps.

输入参数toimodaysfrommmsiuuid

get_vessel_info

Get vessel specifications

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, flag country, callsign and home port. This is reference data, NOT live position — use get_vessel for the current position, or find_vessels to search the registry by attributes.

输入参数imommsiuuid

get_vessel_pro

Get vessel position (enriched)

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 (ATD), a reliable estimated time of arrival (ETA), and current draught. Prefer get_vessel for ordinary position or identity lookups; use get_vessel_pro only when the user asks about the destination or origin port, departure time, arrival time or ETA, or draught, as it is heavier on the backend. If the last known position is stale (the vessel may be out of terrestrial AIS range) and it has a destination and ETA, consider offering estimated_vessel_position to estimate where it is now.

输入参数imommsiuuid

get_vessels_bulk

Get many vessels at once (bulk position)

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). Use this instead of many get_vessel calls when looking up a known set of vessels; for a single vessel use get_vessel.

输入参数imommsiuuid

get_vessels_in_radius

Get vessels in radius (area scan)

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_specific, exclude, nav_status, and include_unknown_type. Returns up to 500 vessels per page, each with its distance (nautical miles) from the center; if more remain, pass the response's 'next' token via the 'next' argument to page through them. Credits are charged per vessel found.

输入参数imolatlonmmsinexttypeuuidradius必填excludeport_uuidnav_statusport_unlocode另有 2 个

get_weather

Get weather for a location

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, …). Specify the location as exactly one of: coordinates (lat+lon), a vessel (mmsi/imo/uuid — weather near its last known position), or a port (port_unlocode/port_uuid). Use mode to choose current conditions (default), a 7-day daily forecast, a 7-day hourly forecast, or any combination. Each weather field has a matching entry in the corresponding *_units object.

输入参数imolatlonmmsimodeuuidport_uuidport_unlocode

intel_casualties

Vessel casualty & incident history

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 with from / to. Part of the Maritime Reports add-on.

输入参数toimofromname

intel_class

Vessel classification & technical particulars

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 or name (set fuzzy for loose name matching), or filter by owner/manager. Part of the Maritime Reports add-on.

输入参数imonamefuzzyupdated_frombeneficial_ownertechnical_managerbeneficial_owner_imotechnical_manager_imo

intel_companies

Maritime company profile

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, so company_imo refers to the company (not a vessel); to find the companies behind a specific ship use intel_ownership. Part of the Maritime Reports add-on.

输入参数namecompany_imoupdated_from

intel_drydock

Vessel drydock & survey schedule

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 vessels due for drydocking in a date range. Part of the Maritime Reports add-on.

输入参数imonamedry_dock_todry_dock_from

intel_engine

Vessel main-engine specifications

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.

输入参数imonamefuzzyupdated_from

intel_info

Maritime Reports add-on status

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-of-AIS positions, and bulk dataset exports. Use this when the user asks whether they have (or what is included in) the add-on, when an intel_* tool reports the add-on is missing, or after the user says they have purchased or updated their subscription.

无需输入参数。

intel_inspections

Vessel Port State Control 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 by imo or name, and optionally bound the period with from / to. Part of the Maritime Reports add-on.

输入参数toimofromname

intel_ownership

Vessel ownership & management chain

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, technical_manager or commercial_manager) to list every vessel that company controls. Part of the Maritime Reports add-on.

输入参数imonameoperatorupdated_frombeneficial_ownertechnical_managercommercial_manager

intel_report_request

Request a bulk intelligence report (async)

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 the matching lookup tool instead (e.g. intel_ownership, intel_inspections). Like all reports it is asynchronous: this returns a report_id and a _PENDING_ status without waiting; submit ONCE, then poll report_status with that report_id until _DONE_, which yields a result_url to hand to the user to download. Do not resubmit while a job is running, and if a report comes back _FAILED_, do not automatically submit a replacement — report the message to the user first. At most 10 reports may be pending per account at once (across every report type), so a retry loop can exhaust the queue. The server never downloads the file itself. Part of the Maritime Reports add-on.

输入参数report_type必填

intel_spd

Ship sale & purchase / demolition records

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 imo or name, and optionally bound the period with from / to. Part of the Maritime Reports add-on.

输入参数toimofromname

report_list

List async reports

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 earlier and its id was lost. Listing is free and never re-runs a report.

无需输入参数。

report_request

Request an async report

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_url. Do not resubmit while a job is running. If a report comes back _FAILED_, do not automatically submit a replacement — report the message to the user first. At most 10 reports may be pending per account at once; further submissions are rejected until some finish. When done, give the user the result_url to download; the server never downloads report files itself. Supported report_type values: - request_usage: a FREE log of your account's API usage (endpoint, credits, timestamp); optional from/to (<=31 days), default last month. - vessel_list: the full vessel database (no other parameters). - port_list: the full ports database (no other parameters). - inradius_history: all vessels that passed through an area in a time window; REQUIRES lat, lon, radius (<=50 NM), from and to (<=7 days apart). Note: vessel_list, port_list and inradius_history consume API credits (vessel_list and inradius_history can be substantial) — it's good to tell the user before submitting. For the add-on bulk datasets (ownership, inspections, etc.) use intel_report_request instead.

输入参数tolatlonfromradiusreport_type必填

report_status

Check an async report

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 one has expired, run report_status again for a fresh link. The server never downloads the file itself. _FAILED_ is terminal. Stop polling: it will never become _DONE_ and there will be no result_url. Read the message field and relay it to the user — it is written for a person and explains the cause. Do not resubmit on your own: tell the user what failed and let them decide. If the message points at a parameter the user can correct, offer the corrected submission rather than making it silently. A report going from _IN_PROGRESS_ back to _PENDING_ is an automatic retry, not a failure. Keep polling. Failed reports are not charged, and polling is free — it never re-runs the report or deducts credits.

输入参数report_id必填

sea_route

Schematic sea route between two points

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 route, not a navigable one. It does not account for actual navigation, hazards, traffic separation, drafts or local rules — do NOT use it for real-world sailing. Use it for estimating distance and travel time, visualizing the approximate path/shape, and similar analysis. Part of the Maritime Reports add-on.

输入参数lat_tolon_tolat_fromlon_fromport_uuid_toport_uuid_fromport_unlocode_toport_unlocode_from

版本历史

1
  1. v1.0.0最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Datalastic 集成