com.berthtime/berthtime · v1.0.4 · communication
BerthTime is healthy: it completed an MCP handshake in 1381 ms and exposes 18 tools.
Track ocean containers and shipments: live ETAs, delays, carrier events and share links.
Endpoint: https://berthtime.com/api/v1/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 18 |
| Latency | 1381 ms |
| Last checked (UTC) | 2026-11-06T09:15:44.914Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-06T09:15:44.914Z | Healthy | 1381 |
list_companies | Who this connection acts as (user or API key), its default company (name, @handle, plan) and every company it may act for, with read or read + write access in each (a.k.a. whoami). Company tools take `company` (id, @handle or name) to pick one. |
list_shipments | List the company's tracked shipments, newest first, with carrier, POL/POD, phase, ETA and delay. Filter by status, carrier SCAC, phase, tag, ETA window or free-text search (reference, customer reference, container number, vessel). |
list_shared_shipments | Shipments other companies (network connections) shared with this company, read-only: owner @handle, carrier, POL/POD, phase, ETA, and open tracking requests (filter=requests). They are not the company's own shipments: the other tools do not see them. |
get_shipment | One shipment by BerthTime id, tracked reference or container number: summary, route (POL, transshipments, POD with actual/estimated times), current position estimate, ETA and the latest actual events. |
get_shipment_events | The DCSA-style event timeline of a shipment (gate in, load, departure, arrival, discharge, ...), oldest first. ACT = actual, EST = estimated, PLN = planned. |
arriving_soon | Active shipments whose ETA falls within the next N days (default 7), soonest first. |
delayed_shipments | Active shipments whose ETA has slipped versus the first ETA BerthTime saw, by at least min_delay_hours (default 24), most delayed first. |
detect_reference | Guess whether a number is a container (ISO 6346 check digit), bill of lading or booking number, and which carrier issued it. Stores nothing. |
list_carriers | Carriers BerthTime knows (SCAC, name), which reference types each supports, and whether tracking is live today. |
get_usage | The company's plan and billable shipments for a month (default: this month): included allowance, used, overage, cost so far, trial end. A shipment counts once per month when the carrier returned data for it. |
list_notification_rules | The company's email alert rules (delay over N days, arrived, delivered, tracking failed), their scope (all shipments, a tag or a carrier) and recipient counts. Read only. |
list_tickets | The company's support requests to the BerthTime team (number BT-1234, subject, status, last activity). Internal staff notes are never included. |
track_shipment | Start tracking a container, bill of lading or booking number. Type and carrier are auto-detected when omitted. Already tracked references are returned as-is (archived ones are re-activated). Requires an API key with the write scope. |
refresh_shipment | Queue an immediate re-fetch of a shipment from the carrier. Requires write scope. Shipments refresh automatically every few hours, so only use this when the user asks: at most once per shipment every 30 minutes, and a daily quota per company. |
get_share_link | The shipment's public read-only tracking link (URL anyone can open without a login), with view count and expiry, if it has one. Requires write scope. |
create_share_link | Create a public read-only tracking link for a shipment, or return the active one. Anyone with the URL sees status, ETA, route and events (no tags or company data). Disable or regenerate it in the web app. Requires write scope. |
create_ticket | Open a support request with the BerthTime team on behalf of the user (only when the user asks to contact support). The team answers by email and in the web app. Requires write scope. |
archive_shipment | Stop tracking a shipment (history is kept; track_shipment re-activates it). Requires write scope. |