# Septa (npm · @pipeworx/mcp-septa)

SEPTA MCP — Philadelphia SEPTA real-time transit (www3.septa.org/api, keyless)

- 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-septa/septa-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-septa/septa-mcp)
- npm · `@pipeworx/mcp-septa`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-septa/pipeworx-mcp-septa.md), [page](https://verifymcp.io/servers/pipeworx-io-septa/pipeworx-mcp-septa)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-septa`
- 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-septa).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 968 tokens (~193/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Septa MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

- [functional improvement] Stability: unverified → 0.23
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (5)

### `septa_rail_arrivals` (~185 tokens)

Philadelphia SEPTA Regional Rail departures board for a station — the next trains leaving, grouped Northbound/Southbound with train number, line, destination, scheduled vs estimated departure time, live status ("On Time" or minutes late), and track. Station names are matched forgivingly ("30th street", "ardmore", "suburban" all work). Example: septa_rail_arrivals({ station: "Suburban Station", results: 8 })

Input parameters:

- `results` (number): Departures to return per direction (default 8, max 30)
- `station` (string, required): Regional Rail station name, e.g. "Suburban Station", "Gray 30th Street" (accepts "30th Street"), "Temple University", "Ardmore", "Airport Terminal B". Partial names are fuzzy-matched to the official…

### `septa_next_to_arrive` (~173 tokens)

Next SEPTA Regional Rail trains from an origin station to a destination station in Philly — direct trains and connecting itineraries (with transfer station), departure/arrival times, and live delay status. Answers "when is the next train from X to Y" in Philadelphia. Example: septa_next_to_arrive({ orig: "Suburban Station", dest: "Airport Terminal B", n: 3 })

Input parameters:

- `dest` (string, required): Destination Regional Rail station, e.g. "Airport Terminal B", "Ardmore" (fuzzy-matched)
- `n` (number): How many upcoming trains to return (default 3, max 10)
- `orig` (string, required): Origin Regional Rail station, e.g. "Suburban Station", "Fox Chase" (fuzzy-matched)

### `septa_train_view` (~163 tokens)

Live positions of every SEPTA Regional Rail train currently running in the Philadelphia region — train number, line, destination, current and next stop, minutes late, and lat/lon. Answers "is my train late" and "where is train 456". Optionally filter to one line. Example: septa_train_view({ line: "Paoli/Thorndale" })

Input parameters:

- `line` (string): Optional Regional Rail line filter: Airport, Chestnut Hill East, Chestnut Hill West, Cynwyd, Fox Chase, Lansdale/Doylestown, Manayunk/Norristown, Media/Wawa, Paoli/Thorndale, Trenton, Warminster, Wes…

### `septa_bus_positions` (~181 tokens)

Live SEPTA bus and trolley vehicle positions for a route in Philadelphia — each vehicle with direction, destination, next stop, minutes late, estimated seat availability (crowding), and lat/lon. Buses use route numbers ("23", "47"); trolleys use SEPTA Metro codes T1-T5, G1 (Girard), D1/D2 (Media/Sharon Hill) — legacy trolley numbers like "10" are auto-translated to T1. Example: septa_bus_positions({ route: "23" })

Input parameters:

- `route` (string, required): Bus route number ("23", "47", "66") or trolley code ("T1"-"T5", "G1", "D1", "D2"; legacy trolley numbers 10/34/13/11/36/15/101/102 also accepted)

### `septa_alerts` (~214 tokens)

SEPTA service alerts, advisories, detours, and suspensions for Philadelphia transit. Pass a route to check one line: a bus number ("23"), a trolley ("T1" or legacy "10"), a Regional Rail line name ("Paoli/Thorndale", "West Trenton", "Airport"), a subway ("Broad Street Line", "Market-Frankford Line", "NHSL"), or a raw route_id ("bus_route_23", "trolley_route_10", "rr_route_pao"). Omit route to list every route with an active alert system-wide. Example: septa_alerts({ route: "Paoli/Thorndale" })

Input parameters:

- `route` (string): Route to check. Bus number ("23"), trolley ("T1" or "10"), rail line name ("Media/Wawa", "Trenton"), subway ("MFL", "BSL", "NHSL"), or raw route_id ("rr_route_pao"). Omit for all active alerts.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Septa MCP server?

Septa is an MCP server listed in the public MCP registry as io.github.pipeworx-io/septa. SEPTA MCP, Philadelphia SEPTA real-time transit (www3.septa.org/api, keyless). This page covers its npm package (@pipeworx/mcp-septa).

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

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

Septa exposes 5 tools: septa_rail_arrivals, septa_next_to_arrive, septa_train_view, septa_bus_positions, septa_alerts. Their descriptions and schemas cost roughly 916 tokens of context every time the server is loaded.

### Is the Septa MCP server still maintained?

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

Septa 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-septa
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-septa
- Repository: https://github.com/pipeworx-io/mcp-septa
- Website: https://pipeworx.io/packs/septa
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-septa/pipeworx-mcp-septa.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-septa/pipeworx-mcp-septa.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-septa/pipeworx-mcp-septa