Remote MCP · Endpoint

Fra Rail Safety MCP server

No. Fra Rail Safety answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://gateway.pipeworx.io/fra-rail-safety/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/fra-rail-safety
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
FRA Rail Safety — US railroad accidents and highway-rail grade crossing incidents reported to the…
Listing
From the official MCP registry (active).
Recent checks of Fra Rail Safety
CheckedResultHandshake
43 minutes agoHandshake completed85 ms
8 days agoHandshake completed202 ms
9 days agoHandshake completed67 ms
11 days agoHandshake completed120 ms
12 days agoHandshake completed58 ms
13 days agoHandshake completed108 ms
14 days agoHandshake completed168 ms
15 days agoHandshake completed125 ms
16 days agoHandshake completed540 ms
19 days agoHandshake completed57 ms
22 days agoHandshake completed85 ms
24 days agoHandshake completed522 ms
26 days agoHandshake completed116 ms
28 days agoHandshake completed85 ms

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

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