Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Apm Terminals

NPM · @PIPEWORX/MCP-APM-TERMINALS · 2 COMPONENTS

APM Terminals container and vessel API

+15 this week 67 Trust /100

Last scanned (3 hours ago)

Scores higher than 38% of npm servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2414 tokens (~482/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 52

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Analysed npm/@pipeworx/mcp-apm-terminals@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~2,358 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
container_event_history ~457

Full lifecycle event history for one or more containers at a named APM Terminals facility — creation, booking/EDO reservation, vessel discharge, yard moves, operator changes, storage updates — each event timestamped, sourced directly from the terminal operating system. Look up by container number(s) at one terminal. Requires an API key (OAuth2 client credentials) — see _apiKey.

NameTypeReqDescription
_apiKeystring–OAuth2 credentials as "<consumer_key>:<consumer_secret>" from a free APM Terminals API Store developer account (https://developer.apmterminals.com/) — sign up, accept the free Data Services Plan, reg…
asset_idstringyesOne or more container numbers, comma-separated, e.g. "TCLU1619533,MRSU3638119".
facility_codestringyesThe terminal's UN/LOCODE, e.g. "USLAX" (Los Angeles), "NLMSV" (Maasvlakte II, Rotterdam), "ESALG" (Algeciras), "ESBCN" (Barcelona), "USMOB" (Mobile), "USNWK" (Port Elizabeth), "USMIA" (Miami), "MAPTM…

No output schema declared.

No examples provided.

empty_container_returns ~442

Empty-container-return status at a named APM Terminals facility: whether a container has been returned empty and the gate-in date/time, sourced directly from the terminal operating system. Look up by one or more container numbers at one terminal. Requires an API key (OAuth2 client credentials) — see _apiKey.

NameTypeReqDescription
_apiKeystring–OAuth2 credentials as "<consumer_key>:<consumer_secret>" from a free APM Terminals API Store developer account (https://developer.apmterminals.com/) — sign up, accept the free Data Services Plan, reg…
asset_idstringyesOne or more container numbers, comma-separated, e.g. "MRKU7137914,MRKU0562064".
facility_codestringyesThe terminal's UN/LOCODE, e.g. "USLAX" (Los Angeles), "NLMSV" (Maasvlakte II, Rotterdam), "ESALG" (Algeciras), "ESBCN" (Barcelona), "USMOB" (Mobile), "USNWK" (Port Elizabeth), "USMIA" (Miami), "MAPTM…

No output schema declared.

No examples provided.

export_booking_enquiry ~456

Export booking status at a named APM Terminals facility: receiving window, cargo cut-off, vessel ETD, container counts received/preadvised/VGM-received, and per-container readiness for load, sourced directly from the terminal operating system. Look up by one or more booking reference numbers at one terminal. Requires an API key (OAuth2 client credentials) — see _apiKey.

NameTypeReqDescription
_apiKeystring–OAuth2 credentials as "<consumer_key>:<consumer_secret>" from a free APM Terminals API Store developer account (https://developer.apmterminals.com/) — sign up, accept the free Data Services Plan, reg…
asset_idstringyesOne or more booking reference numbers, comma-separated, e.g. "205327590,CTR0201633".
facility_codestringyesThe terminal's UN/LOCODE, e.g. "USLAX" (Los Angeles), "NLMSV" (Maasvlakte II, Rotterdam), "ESALG" (Algeciras), "ESBCN" (Barcelona), "USMOB" (Mobile), "USNWK" (Port Elizabeth), "USMIA" (Miami), "MAPTM…

No output schema declared.

No examples provided.

import_availability ~490

Container-level import status at a named APM Terminals facility, sourced directly from the terminal operating system: ready-for-delivery, container state (advised/inbound/yard/loaded/departed/retired), discharge time, yard location, freight/customs holds, demurrage owed, storage-paid-through date, vessel and appointment details. Look up by container number(s) or Bill of Lading number(s) at one terminal. Requires an API key (OAuth2 client credentials) — see _apiKey.

NameTypeReqDescription
_apiKeystring–OAuth2 credentials as "<consumer_key>:<consumer_secret>" from a free APM Terminals API Store developer account (https://developer.apmterminals.com/) — sign up, accept the free Data Services Plan, reg…
asset_idstringyesOne or more container IDs or Bill of Lading numbers, comma-separated, e.g. "WFHU5080179,EGHU9044403".
facility_codestringyesThe terminal's UN/LOCODE, e.g. "USLAX" (Los Angeles), "NLMSV" (Maasvlakte II, Rotterdam), "ESALG" (Algeciras), "ESBCN" (Barcelona), "USMOB" (Mobile), "USNWK" (Port Elizabeth), "USMIA" (Miami), "MAPTM…

No output schema declared.

No examples provided.

terminal_vessel_schedule ~513

Vessel arrival/departure schedule at a named APM Terminals facility — scheduled, latest and actual ETA/ETD, cargo and reefer cut-off times, berth, operator and shipping lines, covering vessels calling the terminal in the past 7 and upcoming 14 days. Look up by vessel name or vessel Lloyds code, optionally narrowed by inbound/outbound voyage number. Requires an API key (OAuth2 client credentials) — see _apiKey.

NameTypeReqDescription
_apiKeystring–OAuth2 credentials as "<consumer_key>:<consumer_secret>" from a free APM Terminals API Store developer account (https://developer.apmterminals.com/) — sign up, accept the free Data Services Plan, reg…
asset_idstringyesA single vessel name or vessel Lloyds code, e.g. "MAERSK NORTHAMPTON". Only one vessel per call.
facility_codestringyesThe terminal's UN/LOCODE, e.g. "USLAX" (Los Angeles), "NLMSV" (Maasvlakte II, Rotterdam), "ESALG" (Algeciras), "ESBCN" (Barcelona), "USMOB" (Mobile), "USNWK" (Port Elizabeth), "USMIA" (Miami), "MAPTM…
inbound_voyage_numberstring–Optional inbound voyage number to narrow the match.
outbound_voyage_numberstring–Optional outbound voyage number to narrow the match.

No output schema declared.

No examples provided.

Install

How do I install the Apm Terminals MCP server?

Apm Terminals runs locally as an npm package, launched with npx -y @pipeworx/mcp-apm-terminals. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-apm-terminals

# add to Claude Code
claude mcp add pipeworx-io-apm-terminals -- npx -y @pipeworx/mcp-apm-terminals
Common questions

What is the Apm Terminals MCP server?

Apm Terminals is an MCP server listed in the public MCP registry as io.github.pipeworx-io/apm-terminals. APM Terminals container and vessel API. This page covers its npm package (@pipeworx/mcp-apm-terminals).

Is the Apm Terminals MCP server safe to use?

Apm Terminals scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Apm Terminals MCP server expose?

Apm Terminals exposes 5 tools: import_availability, export_booking_enquiry, empty_container_returns, terminal_vessel_schedule, container_event_history. Their descriptions and schemas cost roughly 2,358 tokens of context every time the server is loaded.

Is the Apm Terminals MCP server still maintained?

Apm Terminals is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Apm Terminals MCP server under?

Apm Terminals declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Apm Terminals MCP server?

VerifyMCP ran 15 checks on Apm Terminals, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Apm Terminals: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.