Remote MCP · Endpoint

511 Sf Bay MCP server

No. 511 Sf Bay answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://gateway.pipeworx.io/511-sf-bay/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/511-sf-bay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
930 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
511 SF Bay Transit MCP — live departures, vehicle positions and service alerts for every transit…
Listing
From the official MCP registry (active).
Recent checks of 511 Sf Bay
CheckedResultHandshake
20 minutes agoHandshake completed930 ms
8 days agoHandshake completed209 ms
9 days agoHandshake completed160 ms
11 days agoHandshake completed159 ms
12 days agoHandshake completed202 ms
13 days agoHandshake completed109 ms
14 days agoHandshake completed85 ms
15 days agoHandshake completed108 ms
16 days agoHandshake completed174 ms
19 days agoHandshake completed67 ms
21 days agoHandshake completed1.07 s
24 days agoHandshake completed107 ms
26 days agoHandshake completed84 ms
28 days agoHandshake completed64 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with 511 Sf Bay and makes no claim about it beyond what these checks measured.