Bart
BART MCP — San Francisco Bay Area Rapid Transit real-time data (api.bart.gov)
Open the source (opens github.com) https://github.com/pipeworx-io/mcp-bart
Before you use it
- Runs on someone else's server: what you send it leaves your machine.
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: PIPEWORX_API_KEY. Use a key with the least access you can.
What it is
MCP servers from io.github.pipeworx-io.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
@pipeworx/mcp-bart@0.2.1
From the server's entry in the official MCP Registry
Remote endpoint (streamable-http)
https://gateway.pipeworx.io/bart/mcp
From the server's entry in the official MCP Registry
Settings it asks for
PIPEWORX_API_KEYsecret · Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Related
-
Hive Barter
MCP serversMulti-party agent barter — non-cash capability exchange with cryptographic receipts
-
BART Real-Time Transit
MCP serversReal-time BART departures, trip planning, fares, stations, and advisories.
-
BarterBanner
MCP serversTraffic exchange for independent websites: network stats, members, campaigns and site reports.
-
bart-mcp
MCP serversBay Area Rapid Transit departures. No key required.
bart-mcp@1.0.1 -
uta-shield Remote (Barter-enabled)
MCP serversRemote MCP firewall with barter protocol: identity, threat-intel, IoC lookup.
-
Multilateral barter netting for agent services: cycles and chains cleared in kind, zero money.