# 511 Sf Bay (npm · @pipeworx/mcp-511-sf-bay) 511 SF Bay Transit MCP — live departures, vehicle positions and service alerts for every transit… - 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-511-sf-bay/511-sf-bay-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-511-sf-bay/511-sf-bay-mcp) - npm · `@pipeworx/mcp-511-sf-bay`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-511-sf-bay/pipeworx-mcp-511-sf-bay.md), [page](https://verifymcp.io/servers/pipeworx-io-511-sf-bay/pipeworx-mcp-511-sf-bay) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-511-sf-bay` - 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-511-sf-bay). - Clear OSI-approved license (MIT). - Actively maintained (last published 5 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 71/100 - AI-judged instruction clarity (good). - 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. - 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 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. ### Claude ```bash claude mcp add pipeworx-io-511-sf-bay -- npx -y @pipeworx/mcp-511-sf-bay ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-511-sf-bay": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-511-sf-bay" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-511-sf-bay": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-511-sf-bay" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-511-sf-bay -- npx -y @pipeworx/mcp-511-sf-bay ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-511-sf-bay": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-511-sf-bay" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-511-sf-bay --command npx --arg -y --arg @pipeworx/mcp-511-sf-bay ``` ### Hermes ```yaml mcp_servers: pipeworx-io-511-sf-bay: command: "npx" args: ["-y", "@pipeworx/mcp-511-sf-bay"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-511-sf-bay": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-511-sf-bay" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-511-sf-bay -t stdio -c npx -a -y @pipeworx/mcp-511-sf-bay ``` ### Other ```json { "mcpServers": { "pipeworx-io-511-sf-bay": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-511-sf-bay" ] } } } ``` ## 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-03 (score 83, +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. ### 2026-11-01 (score 82, +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 81, +1) - [functional] Package version: 0.2.0 → 0.2.1 ### 2026-10-29 (score 80) First indexed and scored. ## MCP tools (4) ### `bay511_operators` (~117 tokens) 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. Input parameters: - `_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. ### `bay511_stop_predictions` (~180 tokens) 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. Input parameters: - `_apiKey` (string): 511 SF Bay API key. Free from https://511.org/open-data/token. - `agency` (string, required): 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). ### `bay511_vehicles` (~144 tokens) 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. Input parameters: - `_apiKey` (string): 511 SF Bay API key. Free from https://511.org/open-data/token. - `agency` (string, required): 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. ### `bay511_alerts` (~116 tokens) 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". Input parameters: - `_apiKey` (string): 511 SF Bay API key. Free from https://511.org/open-data/token. - `agency` (string, required): Operator code from bay511_operators (e.g. "SF", "BA", "CT"). ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-511-sf-bay/pipeworx-mcp-511-sf-bay#diagnostics ## Score history - 2026-11-05: 83 - 2026-11-04: 83 - 2026-11-03: 83 - 2026-11-02: 82 - 2026-11-01: 82 - 2026-10-31: 81 - 2026-10-30: 81 - 2026-10-29: 80 ## Common questions ### 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. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-511-sf-bay - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-511-sf-bay - Repository: https://github.com/pipeworx-io/mcp-511-sf-bay - Website: https://pipeworx.io/packs/511-sf-bay - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-511-sf-bay/pipeworx-mcp-511-sf-bay.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-511-sf-bay/pipeworx-mcp-511-sf-bay/changelog.json - Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-511-sf-bay/pipeworx-mcp-511-sf-bay.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-511-sf-bay/pipeworx-mcp-511-sf-bay