# Apm Terminals (npm · @pipeworx/mcp-apm-terminals)

APM Terminals container and vessel API

- Trust score: 67/100 (medium)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-apm-terminals/apm-terminals-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-apm-terminals/apm-terminals-mcp)
- npm · `@pipeworx/mcp-apm-terminals`: 67/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-apm-terminals/pipeworx-mcp-apm-terminals.md), [page](https://verifymcp.io/servers/pipeworx-io-apm-terminals/pipeworx-mcp-apm-terminals)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-apm-terminals`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## 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.

### Claude

```bash
claude mcp add pipeworx-io-apm-terminals -- npx -y @pipeworx/mcp-apm-terminals
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-apm-terminals": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-apm-terminals"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-apm-terminals": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-apm-terminals"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-apm-terminals -- npx -y @pipeworx/mcp-apm-terminals
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-apm-terminals": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-apm-terminals"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-apm-terminals --command npx --arg -y --arg @pipeworx/mcp-apm-terminals
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-apm-terminals:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-apm-terminals"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-apm-terminals": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-apm-terminals"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-apm-terminals -t stdio -c npx -a -y @pipeworx/mcp-apm-terminals
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-apm-terminals": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-apm-terminals"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-16 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 52)

First indexed and scored.

## MCP tools (5)

### `import_availability` (~490 tokens)

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.

Input parameters:

- `_apiKey` (string): 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_id` (string, required): One or more container IDs or Bill of Lading numbers, comma-separated, e.g. "WFHU5080179,EGHU9044403".
- `facility_code` (string, required): The 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…

### `export_booking_enquiry` (~456 tokens)

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.

Input parameters:

- `_apiKey` (string): 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_id` (string, required): One or more booking reference numbers, comma-separated, e.g. "205327590,CTR0201633".
- `facility_code` (string, required): The 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…

### `empty_container_returns` (~442 tokens)

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.

Input parameters:

- `_apiKey` (string): 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_id` (string, required): One or more container numbers, comma-separated, e.g. "MRKU7137914,MRKU0562064".
- `facility_code` (string, required): The 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…

### `terminal_vessel_schedule` (~513 tokens)

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.

Input parameters:

- `_apiKey` (string): 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_id` (string, required): A single vessel name or vessel Lloyds code, e.g. "MAERSK NORTHAMPTON". Only one vessel per call.
- `facility_code` (string, required): The 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_number` (string): Optional inbound voyage number to narrow the match.
- `outbound_voyage_number` (string): Optional outbound voyage number to narrow the match.

### `container_event_history` (~457 tokens)

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.

Input parameters:

- `_apiKey` (string): 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_id` (string, required): One or more container numbers, comma-separated, e.g. "TCLU1619533,MRSU3638119".
- `facility_code` (string, required): The 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…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-apm-terminals/pipeworx-mcp-apm-terminals#diagnostics

## Score history

- 2026-11-22: 67
- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 52

## 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-apm-terminals
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-apm-terminals
- Repository: https://github.com/pipeworx-io/mcp-apm-terminals
- Website: https://pipeworx.io/packs/apm-terminals
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-apm-terminals/pipeworx-mcp-apm-terminals.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-apm-terminals/pipeworx-mcp-apm-terminals/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-apm-terminals/pipeworx-mcp-apm-terminals.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-apm-terminals/pipeworx-mcp-apm-terminals
