MCP server list / SF Muni Real-Time Transit
Real-time SF Muni departures, routes, alerts, vehicle positions, and schedules.
Answered:
2 of 4 checks
- Status
- needs a key
- Typical response time
- 266.5 ms
- Last checked
- Latest check:
- This server answered in an earlier check. At its latest check it was: needs a key.Last checked · MCP initialize · 8s limit · HTTP 401 · the call took 186 ms.
- Address
- https://muni-mcp.srivastsh.workers.dev/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.srivastsh/
muni-mcp - Transport
- streamable HTTP
streamable-http - Host
muni-mcp.srivastsh.workers.dev
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 156 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 377 ms | MCP initialize · 8s limit · HTTP 200 | |
| needs a key | 173 ms | MCP initialize · 8s limit · HTTP 401 | |
| needs a key | 186 ms | MCP initialize · 8s limit · HTTP 401 |
Ask for a working one
This server is not answering right now. Say what you needed from it. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.