# Terminal49 (npm · @pipeworx/mcp-terminal49)

Terminal49 MCP — wraps the Terminal49 ocean/container shipment tracking API…

- Trust score: 78/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-terminal49`
- Version: `0.2.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-05.

- **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**: 90/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-terminal49).
  - Clear OSI-approved license (MIT).
  - Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it.
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 678 tokens (~226/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Terminal49 MCP server?

Terminal49 runs locally as an npm package, launched with npx -y @pipeworx/mcp-terminal49. 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-terminal49 -- npx -y @pipeworx/mcp-terminal49
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 78, −1)

- [functional regression] Maintenance: pass → fail

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `terminal49_track` (~318 tokens)

Start tracking an ocean shipment or container by submitting a bill of lading, booking, or container number plus the carrier SCAC. Returns the tracking request id and status (pending -> created/failed). Example: terminal49_track({ request_number: "MEDUFR030802", request_type: "bill_of_lading", scac: "MSCU", _apiKey: "your-key" })

Input parameters:

- `_apiKey` (string, required): Terminal49 API key (create one at https://app.terminal49.com/developers/api-keys).
- `auto_detect_scac` (boolean): Let Terminal49 auto-detect the carrier SCAC instead of supplying one. Defaults to false.
- `ref_numbers` (array): Optional array of your internal reference numbers (e.g. PO numbers) to attach to the shipment.
- `request_number` (string, required): The shipping-line booking number, master bill of lading number, or container number to track, e.g. "MEDUFR030802".
- `request_type` (string): What request_number is: "bill_of_lading", "booking", or "container". Aliases like "bol"/"booking_number" are normalized. Defaults to bill_of_lading.
- `scac` (string): Carrier SCAC (Standard Carrier Alpha Code), e.g. "MSCU" (MSC), "MAEU" (Maersk). Optional if auto_detect_scac is true.
- `shipment_tags` (array): Optional array of tags to attach to the resulting shipment.

### `terminal49_shipment` (~154 tokens)

Get an ocean shipment and its containers: bill of lading, carrier, port of lading (POL), port of discharge (POD), vessel, and ETA. Pass an `id` for a single shipment, or omit it to list recent shipments. Example: terminal49_shipment({ id: "3c9d...", _apiKey: "your-key" })

Input parameters:

- `_apiKey` (string, required): Terminal49 API key (create one at https://app.terminal49.com/developers/api-keys).
- `id` (string): Shipment id (UUID). Omit to list recent shipments instead.
- `page` (number): Page number when listing shipments (optional, defaults to 1).

### `terminal49_container` (~154 tokens)

Get a container by id: current status, terminal holds, demurrage last free day (LFD / pickup_lfd), availability for pickup, and key milestone timestamps. Set include_events=true to also fetch normalized transport events (vessel/rail moves). Example: terminal49_container({ id: "8a1f...", include_events: true, _apiKey: "your-key" })

Input parameters:

- `_apiKey` (string, required): Terminal49 API key (create one at https://app.terminal49.com/developers/api-keys).
- `id` (string, required): Container id (UUID).
- `include_events` (boolean): If true, include transport_events (normalized vessel/rail milestones) in the response.

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Terminal49 MCP server?

Terminal49 is an MCP server listed in the public MCP registry as io.github.pipeworx-io/terminal49. Terminal49 MCP, wraps the Terminal49 ocean/container shipment tracking API… This page covers its npm package (@pipeworx/mcp-terminal49).

### Is the Terminal49 MCP server safe to use?

Terminal49 scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Terminal49 MCP server expose?

Terminal49 exposes 3 tools: terminal49_track, terminal49_shipment, terminal49_container. Their descriptions and schemas cost roughly 626 tokens of context every time the server is loaded.

### Is the Terminal49 MCP server still maintained?

Terminal49 is still listed as active in the MCP registry. We last reached this channel on 5 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 Terminal49 MCP server under?

Terminal49 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 Terminal49 MCP server?

VerifyMCP ran 15 checks on Terminal49, 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 Terminal49: 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-terminal49
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-terminal49
- Repository: https://github.com/pipeworx-io/mcp-terminal49
- Website: https://pipeworx.io/packs/terminal49
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-terminal49/pipeworx-mcp-terminal49.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-terminal49/pipeworx-mcp-terminal49/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-terminal49/pipeworx-mcp-terminal49.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-terminal49/pipeworx-mcp-terminal49