Schedulesmcp

Name: Lane-level ocean carrier schedule RELIABILITY dataset built from first-declared-schedule snapshots: each carrier's originally published ETD/ETA per sailing captured before quiet re-publication, joined to minute-level observed berth times — producing per-lane on-time rate, delay distribution and p90, observed transit-time median/p90, sailing frequency, port congestion/dwell level and tropical-cyclone lane exposure. Delivered over a REST API and a hosted MCP server (12 tools).
Creator: Schedulesmcp

SCHEDULESMCPManage supplier listing

Lane-level ocean carrier schedule RELIABILITY dataset built from first-declared-schedule snapshots: each carrier's originally published ETD/ETA per sailing captured before quiet re-publication, joined to minute-level observed berth times — producing per-lane on-time rate, delay distribution and p90, observed transit-time median/p90, sailing frequency, port congestion/dwell level and tropical-cyclone lane exposure. Delivered over a REST API and a hosted MCP server (12 tools).

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Schedulesmcp and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Marine ShippingFinancial Exchanges & Data
Instruments: equitiescommodities
Categories

Dataset card

Type: not stated
Format: Tabular — JSON over a REST API plus a hosted remote MCP server (Streamable HTTP, Bearer key) with sub-second cached responses; the web app is a thin client over the same backbone
Volume: 72,000+ forward sailings, 5,000+ point-to-point lanes across 255 ports, 60+ carriers live, and 4,200+ scored observed port calls, plus rolling 90-day reliability windows per lane-carrier and supplementary port-congestion and cyclone-exposure series
Users: Not disclosed; bounded to a small early customer base — free lane search requires no signup at all, so registered accounts exist only among paid API/MCP key holders (est. tens to low hundreds, inferred from single-maintainer public codebase and volume-quoted monthly plans)
History: 2 years
Update frequency: not stated
Growth: Active — tool count has grown from 6 to 12, coverage counts rise between successive versions of the same marketing copy, the registry listing is recent, and metrics are computed on live rolling 90-day windows; but scale and staffing remain micro (single public maintainer)
Launched: ~2025-2026 — the MCP-native product family (SchedulesMCP / TrackingMCP / LoadingMCP) is new: the published client package sits at version 0.1.0 and the public registry listing was released mid-2026
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site