Datalastic Vessel Tracking & Maritime Intelligence

warnings

mcp.datalastic.com

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

https://mcp.datalastic.com/mcpOAuthMCP 2025-11-25v0.1.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 163 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://auth.datalastic.com/
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓plain, S256
Grant types	authorization_code, implicit, client_credentials, refresh_token, urn:ietf:params:oauth:grant-type:device_code
Scopes	offline_access, offline, openid
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 25 tools listable
Credentials demanded in prose	✕report_request These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 25 tools listed anonymously say in their own descriptions that they need an account or a key (report_request), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

25 tools usable without signing in

The server exposes a public surface before authorization: estimated_vessel_position, find_ports, find_vessels, get_port, get_vessel, get_vessel_history, get_vessel_info, get_vessel_pro, get_vessels_bulk, get_vessels_in_radius, get_weather, intel_casualties, intel_class, intel_companies, intel_drydock, intel_engine, intel_info, intel_inspections, intel_ownership, intel_report_request, intel_spd, report_list, report_request, report_status, sea_route.

Tools

estimated_vessel_positionfind_portsfind_vesselsget_portget_vesselget_vessel_historyget_vessel_infoget_vessel_proget_vessels_bulkget_vessels_in_radiusget_weatherintel_casualtiesintel_classintel_companiesintel_drydockintel_engineintel_infointel_inspectionsintel_ownershipintel_report_requestintel_spdreport_listreport_requestreport_statussea_route

Contract history

24 Aug 2026v0.1.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/datalastic-vessel-tracking-maritime-intelligence/badge.svg)](https://mcpi.app/servers/datalastic-vessel-tracking-maritime-intelligence)