io.github.lxxmng/ocean-schedules

Est-ce que io.github.lxxmng/ocean-schedules est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.lxxmng/ocean-schedules » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 12 outils

• active_cyclones≈ 116 tokens

  Live tropical cyclones (typhoons/hurricanes) currently active on ocean trade lanes — name, basin, category, center position, max wind, pressure and movement, from CMA (NW-Pacific) + NHC (Atlantic/E-Pacific) + JTWC (Indian/Southern Hemisphere) + GDACS (global). Use this to see which storms are at sea right now.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "active_cyclones", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• carrier_league≈ 63 tokens

  Carrier league table — ocean carriers ranked by overall on-time reliability across all tracked lanes.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "carrier_league", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• carrier_reliability≈ 100 tokens

  On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.

  Paramètres, retour & exemple (1)

  Paramètres

  • carrier_code · string · requis
    Carrier SCAC, e.g. MAEU

  Exemple d'appel

  {"name": "carrier_reliability", "arguments": {"carrier_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• compare_lanes≈ 136 tokens

  Compare ocean carriers serving an origin→destination port pair, ranked by on-time reliability and transit time. Use this to decide which line to book.

  Paramètres, retour & exemple (2)

  Paramètres

  • origin · string · requis
    Origin port UN/LOCODE, e.g. CNSHA
  • destination · string · requis
    Destination port UN/LOCODE, e.g. NLRTM

  Exemple d'appel

  {"name": "compare_lanes", "arguments": {"origin": "texte", "destination": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_best_sailings≈ 518 tokens

  Decision query: the best upcoming sailings on a lane, ONE per carrier (next bookable departure), ranked. Filter by date window, max transit days, min on-time reliability, cut-off still open, and direct-vs-transshipment. Use this to answer "what should I book?". etd, eta, cutoff.at and the from/to window are port-local times with no timezone offset (2026-10-01T13:00:00): quote the digits, do not convert; only retrieved_at is UTC.

  Paramètres, retour & exemple (10)

  Paramètres

  • to · string · optionnel
    Latest departure date YYYY-MM-DD (default: +60 days)
  • from · string · optionnel
    Earliest departure date YYYY-MM-DD (default: today)
  • sort · string · optionnel · recommended | reliability | fastest | soonest
    Ranking (default recommended = reliability blended with transit)
  • cutoff · string · optionnel
    Only sailings whose booking cut-off has not passed. Sailings where no cut-off is held are kept by default; each option carries cutoff_status saying which case it is.
  • origin · string · requis
    Origin port UN/LOCODE or name resolves upstream, e.g. CNSHA
  • destination · string · requis
    Destination port UN/LOCODE, e.g. NLRTM
  • transshipment · boolean · optionnel
    true keeps only sailings that change ship, false only sailings proven direct. Omit it for both: a sailing whose routing we do not hold is returned by neither side, because we will not call a sailing direct without evidence.
  • max_transit_days · number · optionnel
    Maximum transit time in days
  • reliability_floor · number · optionnel
    Minimum 90-day on-time %, 0-100
  • cutoff_include_unknown · boolean · optionnel
    Default true. false narrows to sailings where a deadline is actually held and still ahead.

  Exemple d'appel

  {"name": "find_best_sailings", "arguments": {"origin": "texte", "destination": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_sailings≈ 117 tokens

  Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.

  Paramètres, retour & exemple (2)

  Paramètres

  • origin · string · requis
    Origin port UN/LOCODE
  • destination · string · requis
    Destination port UN/LOCODE

  Exemple d'appel

  {"name": "find_sailings", "arguments": {"origin": "texte", "destination": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_schedules≈ 491 tokens

  Published forward sailing schedules on an origin→destination lane: carrier, vessel, voyage, ETD/ETA, cut-offs and routing (leg count, transshipment ports, distance, CO2 per TEU and the port-by-port route_legs where the carrier publishes them; null where they do not), soonest first, from each carrier's own published schedules. Use this to find concrete upcoming departures to book. Every schedule time (published_departure, published_arrival, cut-offs, route_legs times, the from window) is the local time of its own port as the line publishes it, written without a timezone offset (2026-10-01T13:00:00): quote the digits and do not convert them; departure_precision/arrival_precision say minute (a time) or day (a date only); only retrieved_at is UTC and carries an offset; use transit_days for voyage length. The answer also carries carriers: one entry per line with carrier_code, carrier_name and count (its sailings in this answer; the counts add up to count), most first. An entry has error only when that line was asked live for this lane in this request and gave no answer: timeout (no answer in time), failed (error or unreachable), or paused (not asked; it timed out twice in a row here, retried after 6 h). A line that answered it has no sailings carries no error, and a line in error is listed even at count 0.

  Paramètres, retour & exemple (3)

  Paramètres

  • from · string · optionnel
    Earliest departure date as YYYY-MM-DD, with no time and no timezone offset. Must be today or later. Sailings are returned from 00:00 of that date, read in each port's local time, onward. Omit for today.
  • origin · string · requis
    Origin port UN/LOCODE, e.g. CNSHA
  • destination · string · requis
    Destination port UN/LOCODE, e.g. NLRTM

  Exemple d'appel

  {"name": "get_schedules", "arguments": {"origin": "texte", "destination": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lane_storm_exposure≈ 140 tokens

  Whether an origin→destination ocean lane currently passes through an active cyclone's forecast gale field (a "storm-exposed" sailing at risk of weather delay). Omit ports to list every exposed lane.

  Paramètres, retour & exemple (2)

  Paramètres

  • origin · string · optionnel
    Origin port UN/LOCODE, e.g. CNSHA
  • destination · string · optionnel
    Destination port UN/LOCODE, e.g. USLAX

  Exemple d'appel

  {"name": "lane_storm_exposure", "arguments": {"origin": "texte", "destination": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• port_congestion≈ 139 tokens

  Fused port-congestion signal for a port (UN/LOCODE): effective level (mild/moderate/severe), expected added wait in days (for ETA-band widening), a 0–1 confidence, and the independent readings behind it — measured vessel waiting times, port-call throughput and AIS wait/density.

  Paramètres, retour & exemple (1)

  Paramètres

  • port · string · requis
    Port UN/LOCODE, e.g. NLRTM

  Exemple d'appel

  {"name": "port_congestion", "arguments": {"port": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• port_reliability≈ 92 tokens

  Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.

  Paramètres, retour & exemple (1)

  Paramètres

  • port · string · requis
    Port UN/LOCODE, e.g. NLRTM

  Exemple d'appel

  {"name": "port_reliability", "arguments": {"port": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• transit_time≈ 139 tokens

  Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.

  Paramètres, retour & exemple (3)

  Paramètres

  • origin · string · requis
    Origin port UN/LOCODE
  • destination · string · requis
    Destination port UN/LOCODE
  • carrier_code · string · optionnel
    Optional carrier SCAC to filter

  Exemple d'appel

  {"name": "transit_time", "arguments": {"origin": "texte", "destination": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• watch_lane≈ 279 tokens

  Watch a lane for schedule alerts (PAID): get emailed when a sailing on it is blanked, a booking cut-off is about to close, or a sailing slips. Also alerts on reliability drops. Returns the created watch.

  Paramètres, retour & exemple (7)

  Paramètres

  • origin · string · requis
    Origin port UN/LOCODE, e.g. CNNGB
  • alert_slip · boolean · optionnel
    Alert when a sailing slips vs schedule (default true)
  • alert_blank · boolean · optionnel
    Alert on suspected blank sailings (default true)
  • destination · string · requis
    Destination port UN/LOCODE, e.g. NLRTM
  • alert_cutoff · boolean · optionnel
    Alert when a booking cut-off is closing (default true)
  • carrier_code · string · optionnel
    Optional SCAC to scope the watch to one carrier
  • cutoff_lead_hours · number · optionnel
    Hours before cut-off to alert (default 48)

  Exemple d'appel

  {"name": "watch_lane", "arguments": {"origin": "texte", "destination": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.schedulesmcp.com/mcp