Septa
NPM · @PIPEWORX/MCP-SEPTA · 2 COMPONENTS
SEPTA MCP — Philadelphia SEPTA real-time transit (www3.septa.org/api, keyless)
Available components
Last scanned (9 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-septa). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 5 Nov 26 +3
- Stability: unverified → 0.23 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ 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-septa@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-septa |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-septa/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692346492 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f4a86eb74332bd794ab862013d75880ab470f2ba2c3fde634a919882a7b7ccc28b97a215fb304fc6d91ff56caca7682da2e1b844966cc55ad55cfe66c |
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 →
septa_alerts ~214
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
septa_bus_positions ~181
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| route | string | yes | 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) |
No output schema declared.
No examples provided.
septa_next_to_arrive ~173
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 })
| Name | Type | Req | Description |
|---|---|---|---|
| dest | string | yes | 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 | yes | Origin Regional Rail station, e.g. "Suburban Station", "Fox Chase" (fuzzy-matched) |
No output schema declared.
No examples provided.
septa_rail_arrivals ~185
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 })
| Name | Type | Req | Description |
|---|---|---|---|
| results | number | – | Departures to return per direction (default 8, max 30) |
| station | string | yes | 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… |
No output schema declared.
No examples provided.
septa_train_view ~163
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-septa
claude mcp add pipeworx-io-septa -- npx -y @pipeworx/mcp-septa
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.