Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
BerthTime is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
18
tools declared
remote
at its publisher
—
calls last 7d
What it does
Track ocean containers and shipments: live ETAs, delays, carrier events and share links.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http berthtime-mcp https://berthtime.com/api/v1/mcp
# 2 — ask your agent for something these tools do
# list_companies, list_shipments, list_shared_shipments and 15 more
BerthTime costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BEAll 1 server
berthtime1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http berthtime-mcp https://berthtime.com/api/v1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Who this connection acts as (user or API key) and every company it may act for, with read or read + write access in each (a.k.a. whoami). Call it first when the user belongs to several companies or a call says access is denied; then pass company (id, @handle or exact name) to the other tools. No arguments. Returns: acting_as {type, name, email or prefix, app}, connection (api_key or oauth), all_
No parameter schema on file.
List or search the company's own tracked shipments, newest first. Use it to find a shipment (free-text q: reference, customer reference, container number, vessel) or to filter by status (default active), carrier SCAC, phase, tag, ETA window (eta_after / eta_before, ISO 8601) or predicted eta_risk. For one shipment's full detail use get_shipment; for the next N days use list_arriving_shipments; f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| status | string | no | active (default) = being tracked; archived; or all. |
| carrier | string | no | Carrier SCAC, e.g. MSCU, MAEU. |
| q | string | no | Search text: reference, customer reference, container number or vessel name. |
| phase | string | no | Only shipments in this phase: pending (no carrier data yet), booked, in_transit, arrived or delivered. |
| tag | string | no | Only shipments with this tag (exact tag name, as shown in the web app). |
| eta_after | string | no | Only ETAs at or after this (ISO 8601). |
| eta_before | string | no | Only ETAs at or before this (ISO 8601). |
| eta_risk | string | no | Predicted ETA risk (estimate based on vessel position). |
| limit | integer | no | Page size, 1-100 (default 20). |
| cursor | string | no | next_cursor from a previous call. |
Shipments that other companies (network connections) share with this company, read only, and open tracking requests (filter=requests). They are not the company's own shipments, so list_shipments, get_shipment and the write tools do not see them. All arguments are optional: filter (all or requests), free-text q. Returns: shipments[] {id, reference, ref_type, carrier, carrier_name, customer_refere
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| filter | string | no | all (default), or requests = open tracking requests only. |
| q | string | no | Search text: reference, customer reference, container number or vessel name. |
| limit | integer | no | Page size, 1-100 (default 20). |
| cursor | string | no | next_cursor from a previous call. |
Everything about one shipment: summary, route (POL, transshipments, POD with actual and estimated times), current position estimate, carrier ETA and predicted ETA, and the latest actual events. Use it for "where is X" questions; for the full event history use get_shipment_events. shipment (required) is the BerthTime id, the tracked reference, or a container number on the shipment. Optional `even
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| shipment | string | yes | BerthTime shipment id, or the tracked reference (container, bill of lading or booking number), or a container number on the shipment. |
| events | integer | no | How many of the latest events to include. |
The full DCSA-style event timeline of one shipment (gate in, load, departure, arrival, discharge, ...), oldest first. Use it when the user wants the history; get_shipment already includes the last few actual events. shipment (required) is the BerthTime id, the tracked reference, or a container number on the shipment. Optional: classifier (ACT actual, EST estimated, PLN planned; default all), lim
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| shipment | string | yes | BerthTime shipment id, or the tracked reference (container, bill of lading or booking number), or a container number on the shipment. |
| limit | integer | no | Most recent N events (returned oldest first). |
| classifier | string | no | ACT actual, EST estimated, PLN planned. Default: all. |
Active shipments not yet arrived whose carrier ETA falls within the next N days, soonest first. Use it for "what arrives this week"; for an exact date range or other filters use list_shipments with eta_after / eta_before. All arguments are optional: days (1-120, default 7), limit (1-200, default 50). Returns: days, shipments[] {id, reference, ref_type, carrier, customer_reference, status, tracking
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| days | integer | no | Look-ahead window in days from now. |
| limit | integer | no | Maximum shipments returned, 1-200 (default 50). |
Active shipments whose carrier ETA has slipped versus the first ETA BerthTime saw, by at least min_delay_hours, most delayed first. Use it for "what is late"; for shipments predicted to be late from the vessel position use list_shipments with eta_risk=likely_late. All arguments are optional: min_delay_hours (0-10000, default 24), limit (1-200, default 50). Returns: min_delay_hours, shipments[] {id
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| min_delay_hours | number | no | Minimum ETA slip vs the first ETA seen, in hours. |
| limit | integer | no | Maximum shipments returned, 1-200 (default 50). |
Check a number before tracking it: is it a container (ISO 6346 check digit), bill of lading or booking number, and which carrier issued it. Stores nothing and needs no company. Use it when the user is unsure what a number is; track_shipment detects on its own. Required: reference (3-64 characters, e.g. MSCU1234566). Returns: reference, ref_type, carrier_scac, carrier_name, confidence, check_digit_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reference | string | yes | Container, bill of lading or booking number. |
The carriers BerthTime knows: SCAC, name, which reference types each supports and whether tracking is live today. Use it to find the SCAC for track_shipment's carrier or to answer "do you support X". Optional: live_only (default false). Returns: carriers[] {scac, name, ref_types, tracking, ...}. No paging (the full list).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| live_only | boolean | no | Only carriers with live tracking today. |
The company's plan and billable shipments for one month: included allowance, used, overage, cost so far and trial end. A shipment counts once per month when the carrier returned data for it. Use it for plan, quota or billing questions. Optional: month (YYYY-MM, UTC; default this month), include_shipments (default false) to list the counted shipments. Returns: month, plan, plan_name, included (null
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| month | string | no | Calendar month YYYY-MM (UTC). Default: this month. |
| include_shipments | boolean | no | Also list the counted shipments. |
The company's email alert rules (delay over N days, arrived, delivered, tracking failed), their scope (all shipments, a tag or a carrier) and how many people get them. Read only: rules are created and changed in the web app (Settings > Notifications). Optional: include_inactive (default false) to add paused rules. Returns: rules[] {id, name, summary, rule_type, delay_days, delay_mode, failure_coun
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| include_inactive | boolean | no | Also list paused rules. |
The company's support requests to the BerthTime team, most recent activity first. Use it to check the status of a request; to open one use create_support_request. Internal staff notes are never included. Optional: status (active = open + pending, the default; open, pending, resolved, closed or all), limit (1-100, default 20). Returns: tickets[] {id, number (BT-1234), subject, topic, status, priori
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| status | string | no | active = open + pending (default) |
| limit | integer | no | Maximum requests returned, 1-100 (default 20). |
Start tracking a container, bill of lading or booking number. Type and carrier are detected when omitted; if the carrier is not recognised the shipment is added but not tracked, and you should call again with carrier (SCAC, see list_carriers). Already tracked references are returned as they are (archived ones are re-activated), so repeating a call is safe. Required: reference (4-64 characters, e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| reference | string | yes | Container (ISO 6346, e.g. MSCU1234566), bill of lading or booking number. |
| ref_type | string | no | Auto-detected when omitted. |
| carrier | string | no | Carrier SCAC. Auto-detected when omitted; required when detection fails (see list_carriers). |
| customer_reference | string | no | Your PO / order / file number. |
| tags | array | no | Labels for filtering. |
| booking_number | string | no | Booking number of the same shipment, e.g. with a container reference. |
| bl_number | string | no | Bill of lading number of the same shipment, e.g. with a container reference. |
Set, change or remove the booking and bill of lading numbers of a tracked shipment, or add container numbers to it. Use it when the user gives another number of a shipment already tracked (e.g. the booking of a container); track_shipment would start a new shipment instead. The tracker asks these numbers when the reference fails, and first when the carrier's booking query gives more than its contai
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| shipment | string | yes | BerthTime shipment id, or the tracked reference (container, bill of lading or booking number), or a container number on the shipment. |
| booking_number | string | no | Booking number to set or change; an empty string removes it. Omit to leave it as it is. |
| bl_number | string | no | Bill of lading number to set or change; an empty string removes it. Omit to leave it as it is. |
| containers | array | no | Container numbers (ISO 6346) to add to the shipment. Numbers already on it are ignored. |
The shipment's current public read-only tracking link (a URL anyone can open without logging in), if it has one. Use it before sending a link; use create_share_link when there is none. shipment (required) is the BerthTime id, the tracked reference, or a container number on the shipment. Returns: shipment_id, share_link {url, active, expires_at, view_count, ...} or null. Needs write access: a rea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| shipment | string | yes | BerthTime shipment id, or the tracked reference (container, bill of lading or booking number), or a container number on the shipment. |
Create a public read-only tracking link for a shipment, or return the active one (safe to repeat). Anyone with the URL sees status, ETA, route and events, but no tags or company data. Disable or regenerate it in the web app. shipment (required) is the BerthTime id, the tracked reference, or a container number on the shipment. Returns: shipment_id, created (false = the existing link), share_link
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| shipment | string | yes | BerthTime shipment id, or the tracked reference (container, bill of lading or booking number), or a container number on the shipment. |
Open a support request with the BerthTime team on behalf of the user. Only when the user asks to contact support or report a problem; to see existing requests use list_support_requests. Required: subject (3-200 characters), message (plain text). Optional: topic (support, sales, billing, partnership, other; default support), priority (normal or high, high only when the user says it is urgent). Retu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| subject | string | yes | Short summary of the request, e.g. 'Wrong ETA on MSCU1234566'. |
| message | string | yes | What the user needs help with, in plain text. |
| topic | string | no | What the request is about (default support). |
| priority | string | no | high only when the user says it is urgent (default normal). |
Stop tracking a shipment. Its history is kept and track_shipment with the same reference re-activates it. Only when the user asks to stop or remove a shipment. shipment (required) is the BerthTime id, the tracked reference, or a container number on the shipment. Returns: shipment_id, status (archived). Archiving an archived shipment changes nothing. Needs write access: a read + write API key, or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | no | Which company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company. |
| shipment | string | yes | BerthTime shipment id, or the tracked reference (container, bill of lading or booking number), or a container number on the shipment. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BerthTime or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.4 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest1163e850eb459a93a5b4bb29e1bb77e87d6d22a06a914ce130afec2a97d81d87
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_companies | no tags | |
| list_shipments | no tags | |
| list_shared_shipments | no tags | |
| get_shipment | no tags | |
| get_shipment_events | no tags | |
| list_arriving_shipments | no tags | |
| list_delayed_shipments | no tags | |
| detect_reference | no tags | |
| list_carriers | no tags | |
| get_usage | no tags | |
| list_alert_rules | no tags | |
| list_support_requests | no tags | |
| track_shipment | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| update_shipment_identifiers | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_share_link | state-write | state-write: declares readOnlyHint: false |
| create_share_link | state-write | state-write: declares readOnlyHint: false |
| create_support_request | state-write | state-write: declares readOnlyHint: false |
| archive_shipment | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1163e850eb459a93
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.4.
1.0.4
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish BerthTime can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.