Skip to content

BerthTime MCP server

com.berthtime/berthtimeberthtime.comstreamable-httpv1.0.4Scanned

Track ocean containers and shipments: live ETAs, delays, carrier events and share links.

18 tools: 1 can delete or cancel things, 6 change things and 11 only read.

Tools: 1 delete, 0 irreversible, 6 write, 11 read.
  • Reads private data · 1
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BerthTime MCP server can do

The BerthTime MCP server is published by berthtime.com, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (1 tool: archive_shipment) and create or change data (6 tools: detect_reference, track_shipment, update_shipment_identifiers, get_share_link and 2 more). 11 tools only read.

1 tool reads private data (list_alert_rules); 4 tools bring in text other people can write (list_alert_rules, track_shipment, update_shipment_identifiers and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

18 tools

Deletes or cancels 1Claude Code: deny
  • archive_shipmentStop tracking a shipment.No findings

    Why it is in this group

    • The name "archive_shipment" says "archive": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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 read + write access granted at sign-in by an owner or admin of the company.

    Annotations the server declares

    • title: Archive shipment
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 6Claude Code: ask
  • create_support_requestOpen a support request with the BerthTime team on behalf of the user.No findings

    Why it is in this group

    • The name "create_support_request" says "create": a word for a change.
    Description, as the server wrote it
    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). Returns: id, number (BT-1234), status, requester_email. The team answers by email and in the web app. Each call opens a new request, so do not repeat it. Needs write access: a read + write API key, or read + write access granted at sign-in by an owner or admin of the company.

    Annotations the server declares

    • title: Contact BerthTime support
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • detect_referenceCheck a number before tracking it: is it a container (ISO 6346 check digit), bill of lading or booking number, and which carrier issued it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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_valid, note, suggested_carrier.

    Annotations the server declares

    • title: Detect reference
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • track_shipmentStart tracking a container, bill of lading or booking number.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.g. MSCU1234566). Optional: ref_type (container, bl, booking), carrier, customer_reference, tags, booking_number and bl_number (the other numbers of the same shipment, e.g. a container with its booking: one shipment, not three). Returns: result (created or exists), shipment {id, reference, ref_type, carrier, customer_reference, status, tracking_status, phase, pol, pod, eta, original_eta, delay_hours, predicted_eta, eta_risk, vessel, containers, booking_number, bl_number, tracked_via}. The first carrier data arrives in the background: check get_shipment a minute later. Counts towards the plan's monthly allowance once the carrier returns data. Needs write access: a read + write API key, or read + write access granted at sign-in by an owner or admin of the company.

    Annotations the server declares

    • title: Track shipment
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • update_shipment_identifiersSet, change or remove the booking and bill of lading numbers of a tracked shipment, or add container numbers to it.Reads text others writeNo findings

    Why it is in this group

    • The name "update_shipment_identifiers" says "update": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 container query (e.g. COSCO). `shipment` (required) is the BerthTime id, the tracked reference, or a container number on the shipment. Optional: booking_number, bl_number (an empty string removes it; omitted = unchanged), containers (ISO 6346, up to 20). At least one of them is required. Returns: shipment {id, reference, ref_type, carrier, customer_reference, status, tracking_status, phase, pol, pod, eta, original_eta, delay_hours, predicted_eta, eta_risk, vessel, containers, booking_number, bl_number, tracked_via}, retracking (true = a re-track was queued). A container number given as booking or B/L, or a malformed number, is an error. Needs write access: a read + write API key, or read + write access granted at sign-in by an owner or admin of the company.

    Annotations the server declares

    • title: Set booking / B/L / containers
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 11Show 11 read-only tools
  • get_shipmentEverything about one shipment: summary, route (POL, transshipments, POD with actual and estimated times), current position estimate, carrier ETA and predicted ETA, and the latest a…No findings

    Why it is in this group

    • The name "get_shipment" says "get": a word for reading.
    Description, as the server wrote it
    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 `events` (0-50, default 5) = how many latest actual events to include. Returns: shipment {id, reference, ref_type, carrier, customer_reference, status, tracking_status, phase, pol, pod, eta, original_eta, delay_hours, predicted_eta, eta_risk, vessel, containers, booking_number, bl_number, tracked_via, last_position, container_remarks}, route {stops[] {role, name, un_locode, arrival, departure}, legs[], current_position} or null, latest_events[], changes[] (the last 10 changes of plan, newest first: {seen_at, source, first, changes[] {field (eta, vessel, pol, pod, transshipments, state), old, new}, eta_delay_hours vs the first ETA}), changes_recorded_since. Unknown reference: an error that suggests list_shipments or track_shipment.

    Annotations the server declares

    • title: Get shipment
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_shipment_eventsThe full DCSA-style event timeline of one shipment (gate in, load, departure, arrival, discharge, ...), oldest first.No findings

    Why it is in this group

    • The name "get_shipment_events" says "get": a word for reading.
    Description, as the server wrote it
    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), limit (most recent N, 1-500, default 50). Returns: shipment_id, reference, events[] {at, timezone, precision, classifier, code, type, description, location, un_locode, vessel, voyage, container}. Times are UTC.

    Annotations the server declares

    • title: Shipment events
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_usageThe company's plan and billable shipments for one month: included allowance, used, overage, cost so far and trial end.No findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.
    Description, as the server wrote it
    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 = unlimited), used, overage, projected_cost, currency, trial_ends_at, trial_active, and with include_shipments: shipments[] {shipment_id, reference, ref_type, first_counted_at, merged}.

    Annotations the server declares

    • title: Plan and usage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_alert_rulesThe 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_alert_rules" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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_count, scope, scope_value, is_active, recipients {all_members, members, extra_emails}}.

    Annotations the server declares

    • title: Email alert rules
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_arriving_shipmentsActive shipments not yet arrived whose carrier ETA falls within the next N days, soonest first.No findings

    Why it is in this group

    • The name "list_arriving_shipments" says "list": a word for reading.
    Description, as the server wrote it
    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_status, phase, pol, pod, eta, original_eta, delay_hours, predicted_eta, eta_risk, vessel, containers, booking_number, bl_number, tracked_via}. No paging: raise limit or narrow days.

    Annotations the server declares

    • title: Arriving soon
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_carriersThe carriers BerthTime knows: SCAC, name, which reference types each supports and whether tracking is live today.No findings

    Why it is in this group

    • The name "list_carriers" says "list": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: List carriers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_companiesWho 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.No findings

    Why it is in this group

    • The name "list_companies" says "list": a word for reading.
    Description, as the server wrote it
    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_companies, default_company and companies[] {id, name, handle, plan, plan_name, role, access, default}.

    Annotations the server declares

    • title: Who am I / my companies
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_delayed_shipmentsActive shipments whose carrier ETA has slipped versus the first ETA BerthTime saw, by at least min_delay_hours, most delayed first.No findings

    Why it is in this group

    • The name "list_delayed_shipments" says "list": a word for reading.
    Description, as the server wrote it
    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, reference, ref_type, carrier, customer_reference, status, tracking_status, phase, pol, pod, eta, original_eta, delay_hours, predicted_eta, eta_risk, vessel, containers, booking_number, bl_number, tracked_via} (delay_hours = the slip). No paging.

    Annotations the server declares

    • title: Delayed shipments
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_shared_shipmentsShipments that other companies (network connections) share with this company, read only, and open tracking requests (filter=requests).No findings

    Why it is in this group

    • The name "list_shared_shipments" says "list": a word for reading.
    Description, as the server wrote it
    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_reference, owner (@handle), owner_name, status, tracking_status, phase, eta, delay_hours, pol, pod, vessel, kind, request_status, paid_by_you, shared_at}, has_more, next_cursor. Paging: limit 1-100 (default 20) and `cursor`.

    Annotations the server declares

    • title: Shipments shared with us
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_shipmentsList or search the company's own tracked shipments, newest first.No findings

    Why it is in this group

    • The name "list_shipments" says "list": a word for reading.
    Description, as the server wrote it
    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; for slipped ETAs use list_delayed_shipments; shipments other companies share with you are in list_shared_shipments. All arguments are optional. Returns: shipments[] {id, reference, ref_type, carrier, customer_reference, status, tracking_status, phase, pol, pod, eta, original_eta, delay_hours, predicted_eta, eta_risk, vessel, containers, booking_number, bl_number, tracked_via}, has_more, next_cursor. Paging: limit 1-100 (default 20); pass next_cursor as `cursor` for the next page.

    Annotations the server declares

    • title: List shipments
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_support_requestsThe company's support requests to the BerthTime team, most recent activity first.No findings

    Why it is in this group

    • The name "list_support_requests" says "list": a word for reading.
    Description, as the server wrote it
    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, priority, last_message_at, last_message_by, message_count, preview}, counts by status.

    Annotations the server declares

    • title: Support requests
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://berthtime.com/.well-known/oauth-protected-resource/api/v1/mcp
Authorization servers
https://berthtime.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://berthtime.com/api/v1/mcp: tools/list returned 18 tools to an anonymous client, including archive_shipment (destructive), detect_reference (write), track_shipment (write), update_shipment_identifiers (write), get_share_link (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_share_link" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_share_link" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 removed.−1 removedView diff
    • Removed:refresh_shipment
  3. Tools6 added, 5 removed, 13 changed.+6 added−5 removed~13 changedView diff

Install

Pinned to version 1.0.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http berthtime https://berthtime.com/api/v1/mcp
claude mcp add --transport http berthtime https://berthtime.com/api/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__berthtime__list_companies",
      "mcp__berthtime__list_shipments",
      "mcp__berthtime__list_shared_shipments",
      "mcp__berthtime__get_shipment",
      "mcp__berthtime__get_shipment_events",
      "mcp__berthtime__list_arriving_shipments",
      "mcp__berthtime__list_delayed_shipments",
      "mcp__berthtime__list_carriers",
      "mcp__berthtime__get_usage",
      "mcp__berthtime__list_alert_rules",
      "mcp__berthtime__list_support_requests"
    ],
    "ask": [
      "mcp__berthtime__detect_reference",
      "mcp__berthtime__track_shipment",
      "mcp__berthtime__update_shipment_identifiers",
      "mcp__berthtime__get_share_link",
      "mcp__berthtime__create_share_link",
      "mcp__berthtime__create_support_request"
    ],
    "deny": [
      "mcp__berthtime__archive_shipment"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as berthtime. Review it before you use it.

Capability tags behind 4 rules
  • mcp__berthtime__list_alert_rules private-data, untrusted-input
  • mcp__berthtime__track_shipment untrusted-input
  • mcp__berthtime__update_shipment_identifiers untrusted-input
  • mcp__berthtime__get_share_link untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.berthtime/berthtime/verify?hash=45b650d63d0018cc9b6aee79e45deefface737c1b8369c9737fdb29442e0c1a9" | jq -e '.changed == false'

Pinned hash 45b650d63d00, from Nov 20, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.berthtime/berthtime/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.berthtime/berthtime
[![Anlyon Radar](https://radar.anlyon.com/badge/com.berthtime/berthtime.svg)](https://radar.anlyon.com/servers/com.berthtime/berthtime)

Source: MCP Registry · repository. Synced Nov 6, 2026, 14:17 UTC.

BerthTime MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BerthTime MCP server safe?

No scan can promise that. What its definitions show: 18 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BerthTime MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: archive_shipment.

Can the BerthTime MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BerthTime MCP server have?

18 tools: 1 destructive, 6 write, 11 read. archive_shipment, detect_reference, track_shipment, update_shipment_identifiers, get_share_link, create_share_link, create_support_request, list_companies and 10 more.

Does the BerthTime MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BerthTime MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BerthTime MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.