# Mbta (npm · @pipeworx/mcp-mbta)

MBTA MCP — Boston real-time transit via the MBTA v3 API (api-v3.mbta.com)

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-mbta`
- 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-mbta).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 795 tokens (~198/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 Mbta MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

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

### 2026-11-04 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 67, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 81, +1)

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

### 2026-10-30 (score 80, +1)

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

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

First indexed and scored.

## MCP tools (4)

### `mbta_departures` (~274 tokens)

Real-time MBTA train arrival and departure predictions at a Boston station — answers "when is the next train Boston", next Red Line subway at South Station, Green Line trolley, commuter rail departures, Silver Line and bus arrivals. Accepts a station name ("South Station", "Harvard") or a place id ("place-sstat"). Falls back to the published schedule when live predictions are empty (common for commuter rail off-peak). Example: mbta_departures({ stop: "South Station", route: "Red" })

Input parameters:

- `_apiKey` (string): Optional: free MBTA v3 API key from api-v3.mbta.com for higher rate limits
- `direction_id` (number): Optional direction filter: 0 or 1 (meaning per route — see direction_destinations from mbta_routes)
- `limit` (number): Max departures to return, 1-30 (default 8)
- `route` (string): Optional route id to filter, e.g. "Red", "Green-B", "CR-Providence", "SL1", "66" (see mbta_routes)
- `stop` (string, required): Station name (e.g. "South Station", "Harvard", "Back Bay") or MBTA place id (e.g. "place-sstat")

### `mbta_routes` (~182 tokens)

List MBTA routes for the Boston subway T, commuter rail, bus, and ferry — route ids, names, and the destination each direction heads toward. type: 0-1 subway/light rail (Red, Orange, Blue, Green, Mattapan), 2 commuter rail, 3 bus (includes Silver Line), 4 ferry. Default returns subway + commuter rail + ferry; pass type 3 for buses. Example: mbta_routes({ type: "2" })

Input parameters:

- `_apiKey` (string): Optional: free MBTA v3 API key from api-v3.mbta.com for higher rate limits
- `type` (string): Route type filter, comma-separable: "0,1" subway, "2" commuter rail, "3" bus, "4" ferry (default "0,1,2,4")

### `mbta_stops` (~141 tokens)

List the stops and stations on an MBTA route — Boston subway T lines, commuter rail lines, bus routes, ferries. Returns stop id, name, municipality, and wheelchair accessibility, in route order. Example: mbta_stops({ route: "Red" }) or mbta_stops({ route: "CR-Worcester" })

Input parameters:

- `_apiKey` (string): Optional: free MBTA v3 API key from api-v3.mbta.com for higher rate limits
- `route` (string, required): Route id from mbta_routes, e.g. "Red", "Green-D", "CR-Providence", "66"

### `mbta_alerts` (~145 tokens)

Active MBTA service alerts — Boston subway T delays, commuter rail disruptions, shuttle replacements, track changes, detours, elevator outages. Filter by route to check one line, e.g. is the Red Line delayed right now. Example: mbta_alerts({ route: "Red" })

Input parameters:

- `_apiKey` (string): Optional: free MBTA v3 API key from api-v3.mbta.com for higher rate limits
- `limit` (number): Max alerts to return, 1-50 (default 15)
- `route` (string): Optional route id to filter, e.g. "Red", "CR-Kingston", "66"

## Diagnostics

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

## Score history

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

## Common questions

### What is the Mbta MCP server?

Mbta is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mbta. MBTA MCP, Boston real-time transit via the MBTA v3 API (api-v3.mbta.com). This page covers its npm package (@pipeworx/mcp-mbta).

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

Mbta 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 Mbta MCP server expose?

Mbta exposes 4 tools: mbta_departures, mbta_routes, mbta_stops, mbta_alerts. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.

### Is the Mbta MCP server still maintained?

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

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

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