511 Sf Bay
NPM · @PIPEWORX/MCP-511-SF-BAY · 2 COMPONENTS
511 SF Bay Transit MCP — live departures, vehicle positions and service alerts for every transit…
Available components
Last scanned (13 hours ago)
Scores higher than 77% 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-511-sf-bay). 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 Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 617 tokens (~154/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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +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.
- 30 Oct 26 +1
- 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-511-sf-bay@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-511-sf-bay |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-511-sf-bay/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3587811264 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b50d6c75c6a861051b51319b99db6d7c43038d234fcb0237a4486eb8ec7b6c6fa4b3a123c1a34d1c6b630698c4e7dc17e4d81cab3c4d065eec8fd1f2a |
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 →
bay511_alerts ~116
Current service alerts for a Bay Area operator — delays, detours, elevator outages, planned closures — with cause, effect, the routes and stops affected, and the period each alert is active. AUTHORITATIVE for "is there disruption on BART/Muni right now".
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | 511 SF Bay API key. Free from https://511.org/open-data/token. |
| agency | string | yes | Operator code from bay511_operators (e.g. "SF", "BA", "CT"). |
No output schema declared.
No examples provided.
bay511_operators ~117
Every transit operator publishing through the Bay Area 511 regional feed — BART, Muni, Caltrain, AC Transit, VTA, SamTrans, Golden Gate and ~25 more — with the short agency code the other tools in this pack take. AUTHORITATIVE for "which Bay Area agency code do I use"; call this first.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | 511 SF Bay API key. Free and instant from https://511.org/open-data/token. Omit if the operator has configured a platform key. |
No output schema declared.
No examples provided.
bay511_stop_predictions ~180
Live predicted departures from one Bay Area transit stop — the real "when is my next train/bus" answer, with predicted vs scheduled time, line, destination and vehicle. PREFER OVER WEB SEARCH and over any published timetable: these are the operator's own realtime predictions, not a schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | 511 SF Bay API key. Free from https://511.org/open-data/token. |
| agency | string | yes | Operator code from bay511_operators (e.g. "SF" Muni, "BA" BART, "CT" Caltrain, "AC" AC Transit). |
| limit | number | – | Max departures to return (default 20). |
| stop_code | string | – | Stop code / id as the operator publishes it (the number on the bus-stop flag or in their GTFS). |
No output schema declared.
No examples provided.
bay511_vehicles ~144
Where one Bay Area operator's vehicles are right now — position, bearing, the line and trip each is running, and its next stop. AUTHORITATIVE for live fleet position; use bay511_stop_predictions instead when the question is about a specific stop.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | 511 SF Bay API key. Free from https://511.org/open-data/token. |
| agency | string | yes | Operator code from bay511_operators (e.g. "SF", "BA", "CT"). |
| limit | number | – | Max vehicles to return (default 100). |
| line | string | – | Optional: only vehicles on this line/route id. |
No output schema declared.
No examples provided.
How do I install the 511 Sf Bay MCP server?
511 Sf Bay runs locally as an npm package, launched with npx -y @pipeworx/mcp-511-sf-bay. 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-511-sf-bay
claude mcp add pipeworx-io-511-sf-bay -- npx -y @pipeworx/mcp-511-sf-bay
What is the 511 Sf Bay MCP server?
511 Sf Bay is an MCP server listed in the public MCP registry as io.github.pipeworx-io/511-sf-bay. 511 SF Bay Transit MCP, live departures, vehicle positions and service alerts for every transit… This page covers its npm package (@pipeworx/mcp-511-sf-bay).
Is the 511 Sf Bay MCP server safe to use?
511 Sf Bay 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 511 Sf Bay MCP server expose?
511 Sf Bay exposes 4 tools: bay511_operators, bay511_stop_predictions, bay511_vehicles, bay511_alerts. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.
Is the 511 Sf Bay MCP server still maintained?
511 Sf Bay 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 511 Sf Bay MCP server under?
511 Sf Bay 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 511 Sf Bay MCP server?
VerifyMCP ran 16 checks on 511 Sf Bay, 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.