# Cta (npm · @pipeworx/mcp-cta)

CTA MCP — Chicago Transit Authority real-time trains ('L') + buses

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-cta`
- 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-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**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-cta).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 997 tokens (~249/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**: 80/100
  - Stability observed for 24 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 Cta MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-21 (score 90, +1)

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

### 2026-11-19 (score 89, +1)

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

### 2026-11-16 (score 88, +1)

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

### 2026-11-14 (score 87, +1)

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

### 2026-11-12 (score 86, +1)

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

### 2026-11-10 (score 85, +1)

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

### 2026-11-08 (score 84, +1)

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

### 2026-11-06 (score 83, +1)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (4)

### `cta_train_arrivals` (~286 tokens)

Real-time Chicago CTA 'L' train arrivals at a station — answers "when is the next train Chicago", next Red Line at Belmont, Blue Line to O'Hare from Clark/Lake. Returns each upcoming train's line color, destination, arrival time and minutes_away, plus approaching / delayed / scheduled-only flags and the platform description. Station accepts a name ("Belmont", "Clark/Lake", "O'Hare") or a 5-digit mapid (e.g. 41320). Example: cta_train_arrivals({ station: "Belmont", route: "Red" })

Input parameters:

- `_apiKey` (string): Optional: your own CTA credentials as "train_key:bus_key" — Train Tracker key (free at transitchicago.com/developers) + Bus Tracker key (free at ctabustracker.com)
- `max` (number): Max arrivals to return, 1-20 (default 8)
- `route` (string): Optional 'L' line filter: Red, Blue, Brown, Green, Orange, Purple, Pink, or Yellow (also disambiguates same-named stations)
- `station` (string, required): Station name (e.g. "Belmont", "Clark/Lake", "O'Hare", "Midway") or 5-digit mapid (e.g. "41320")

### `cta_train_positions` (~178 tokens)

Live Chicago CTA 'L' train positions on one or more lines — where every Red Line, Blue Line, Brown, Green, Orange, Purple, Pink, or Yellow train is right now: lat/lon, heading, next station with ETA, destination, approaching and delayed flags. Answers "where are the Blue Line trains" for the Chicago L. Example: cta_train_positions({ routes: "Red,Blue" })

Input parameters:

- `_apiKey` (string): Optional: your own CTA credentials as "train_key:bus_key" — Train Tracker key (free at transitchicago.com/developers) + Bus Tracker key (free at ctabustracker.com)
- `routes` (string, required): Comma-separated 'L' lines, full color names accepted: "Red", "Red,Blue", "Brown,Purple"

### `cta_bus_predictions` (~328 tokens)

Chicago CTA bus tracker arrival predictions at a bus stop — route, destination, predicted minutes until arrival ("DUE" = arriving now), delay flag, and vehicle id. Pass stop_id (the 4-5 digit stop number posted on CTA bus-stop signs), optionally with route. If you only know the stop by name, pass route + find_stop (a street/intersection fragment like "clark & madison") and the stop is looked up for you. Example: cta_bus_predictions({ route: "22", find_stop: "addison" })

Input parameters:

- `_apiKey` (string): Optional: your own CTA credentials as "train_key:bus_key" — Train Tracker key (free at transitchicago.com/developers) + Bus Tracker key (free at ctabustracker.com)
- `direction` (string): Optional direction to narrow find_stop, e.g. "Northbound", "south"
- `find_stop` (string): Stop-name fragment to look up when stop_id is unknown, e.g. "clark & madison", "michigan & randolph". Requires route.
- `max` (number): Max predictions to return, 1-20 (default 10)
- `route` (string): Optional bus route number to filter, e.g. "22", "66", "X49". Required when using find_stop.
- `stop_id` (string): CTA bus stop id (stpid), the number on the bus-stop sign, e.g. "1926". Comma-separable up to 10.

### `cta_bus_positions` (~153 tokens)

Live Chicago CTA bus positions on a route — every vehicle currently running: lat/lon, heading, destination, delayed flag, and distance along the pattern. Answers "where is the 22 Clark bus right now" via the CTA bus tracker. Example: cta_bus_positions({ route: "22" })

Input parameters:

- `_apiKey` (string): Optional: your own CTA credentials as "train_key:bus_key" — Train Tracker key (free at transitchicago.com/developers) + Bus Tracker key (free at ctabustracker.com)
- `route` (string, required): Bus route number, e.g. "22", "66", "146". Comma-separable up to 10.

## Diagnostics

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

## Score history

- 2026-11-22: 90
- 2026-11-21: 90
- 2026-11-20: 89
- 2026-11-19: 89
- 2026-11-18: 88
- 2026-11-17: 88
- 2026-11-16: 88
- 2026-11-15: 87
- 2026-11-14: 87
- 2026-11-13: 86
- 2026-11-12: 86
- 2026-11-11: 85
- 2026-11-10: 85
- 2026-11-09: 84
- 2026-11-08: 84
- 2026-11-07: 83
- 2026-11-06: 83
- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 54
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Cta MCP server?

Cta is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cta. CTA MCP, Chicago Transit Authority real-time trains ('L') + buses. This page covers its npm package (@pipeworx/mcp-cta).

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

Cta scores 90 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. 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 Cta MCP server expose?

Cta exposes 4 tools: cta_train_arrivals, cta_train_positions, cta_bus_predictions, cta_bus_positions. Their descriptions and schemas cost roughly 945 tokens of context every time the server is loaded.

### Is the Cta MCP server still maintained?

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

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

VerifyMCP ran 16 checks on Cta, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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-cta
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-cta
- Repository: https://github.com/pipeworx-io/mcp-cta
- Website: https://pipeworx.io/packs/cta
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-cta/pipeworx-mcp-cta.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-cta/pipeworx-mcp-cta/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-cta/pipeworx-mcp-cta.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-cta/pipeworx-mcp-cta
