Amtrak
NPM · @PIPEWORX/MCP-AMTRAK · 2 COMPONENTS
Amtrak MCP — live Amtrak train tracking via the community Amtraker API (api-v3.amtraker.com, a…
Available components
Last scanned (7 hours ago)
Scores higher than 76% of npm servers
Category Maps and Location
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-amtrak). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 80
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-amtrak@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-amtrak |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-amtrak/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3587945504 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dfcfde69071b09b4067d477ecfb33156b306a254cd6e7cfce4a7227d577d8d20ab0bcf6012dc8c79ba3c208635c95d07c58237f53cd85ee9dda521497 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
amtrak_routes_active ~84
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({})
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
amtrak_station_board ~189
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max trains to return, 1-15 (default 15) |
| station | string | yes | Amtrak station code (e.g. "CHI", "NYP", "SEA") or station/city name (e.g. "Chicago", "Denver") |
No output schema declared.
No examples provided.
amtrak_station_info ~113
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| station | string | yes | Amtrak station code (e.g. "DEN", "NYP") or station/city name (e.g. "Denver", "New York") |
No output schema declared.
No examples provided.
amtrak_train_status ~213
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| train | string | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-amtrak
claude mcp add pipeworx-io-amtrak -- npx -y @pipeworx/mcp-amtrak
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.