Remote MCP · Endpoint

SafeStreets MCP server

No. SafeStreets answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://safestreets.streetsandcommons.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Poseidon-t/safestreets
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
136 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Walkability and pedestrian safety for any US address: scores, neighborhoods, deadly roads.
Listing
From the official MCP registry (active).
Recent checks of SafeStreets
CheckedResultHandshake
39 minutes agoHandshake completed136 ms
3 days agoHandshake completed195 ms
13 days agoHandshake completed155 ms
13 days agoHandshake completed185 ms
15 days agoHandshake completed137 ms
16 days agoHandshake completed169 ms
17 days agoHandshake completed181 ms
18 days agoHandshake completed129 ms
18 days agoHandshake completed146 ms
20 days agoHandshake completed158 ms
22 days agoHandshake completed149 ms
25 days agoHandshake completed204 ms
27 days agoHandshake completed203 ms

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

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 SafeStreets and makes no claim about it beyond what these checks measured.

SafeStreets MCP server - status, uptime and latency - Glide