# Amtrak (npm · @pipeworx/mcp-amtrak)

Amtrak MCP — live Amtrak train tracking via the community Amtraker API (api-v3.amtraker.com, a…

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-amtrak`
- Version: `0.2.1`
- 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**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-amtrak).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 651 tokens (~162/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.

## Install

### How do I install the Amtrak MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

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

- [functional regression] Security disclosure: unverified → fail
- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (4)

### `amtrak_train_status` (~213 tokens)

Live Amtrak train status and GPS tracking — "where is my Amtrak train", "is train 6 late", "track the California Zephyr". Accepts a train number ("6", "2150") or route name ("Coast Starlight", "Empire Builder"). Returns each active instance of that train: current GPS position, speed, heading, timeliness, next station with ETA and delay minutes, and origin/destination scheduled vs actual times. Data is a community mirror of Amtrak's own tracking feed (api-v3.amtraker.com); positions update about every few minutes. Example: amtrak_train_status({ train: "6" })

Input parameters:

- `train` (string, required): Amtrak train number (e.g. "6", "91", "2150") or route name (e.g. "California Zephyr", "Acela", "Coast Starlight"). Via Rail ("v1") and Brightline ("b5151") trains in the same feed also work.

### `amtrak_station_board` (~189 tokens)

Amtrak station departures/arrivals board — upcoming trains at a station. "What trains are arriving at Chicago Union?", "next train at CHI", "station board for Denver". Accepts a 3-letter Amtrak station code ("CHI", "NYP", "LAX") or a station name ("Chicago", "Portland"). Returns trains currently en route to that station with route, scheduled vs estimated arrival, delay minutes, and status. Live community mirror of Amtrak tracking (api-v3.amtraker.com). Example: amtrak_station_board({ station: "CHI" })

Input parameters:

- `limit` (number): Max trains to return, 1-15 (default 15)
- `station` (string, required): Amtrak station code (e.g. "CHI", "NYP", "SEA") or station/city name (e.g. "Chicago", "Denver")

### `amtrak_routes_active` (~84 tokens)

Summary of ALL currently active Amtrak trains grouped by route — "how many Amtrak trains are running right now", "which Amtrak routes have delays", national system overview. Returns per route: active train count, train numbers, and the worst delay in minutes. Compact; live from a community mirror of Amtrak's tracking feed. Example: amtrak_routes_active({})

### `amtrak_station_info` (~113 tokens)

Amtrak station lookup by code or name — station name, 3-letter code, city/state, street address, timezone, coordinates, and how many trains are currently inbound. "Where is the Amtrak station in Denver?", "what is station code NYP". Example: amtrak_station_info({ station: "Denver" })

Input parameters:

- `station` (string, required): Amtrak station code (e.g. "DEN", "NYP") or station/city name (e.g. "Denver", "New York")

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Amtrak MCP server?

Amtrak is an MCP server listed in the public MCP registry as io.github.pipeworx-io/amtrak. Amtrak MCP, live Amtrak train tracking via the community Amtraker API (api-v3.amtraker.com, a… This page covers its npm package (@pipeworx/mcp-amtrak).

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

Amtrak scores 83 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 Amtrak MCP server expose?

Amtrak exposes 4 tools: amtrak_train_status, amtrak_station_board, amtrak_routes_active, amtrak_station_info. Their descriptions and schemas cost roughly 599 tokens of context every time the server is loaded.

### Is the Amtrak MCP server still maintained?

Amtrak 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 Amtrak MCP server under?

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

## Links

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