Remote MCP · Endpoint

BikeTheRail MCP server

No. BikeTheRail answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://biketherail.org/mcp

The last check completed an MCP handshake.

Registry name
org.biketherail/trails
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
765 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Look up U.S. rail-trails: search, nearby trails, trail facts, trailheads and closures.
Listing
From the official MCP registry (active).
Recent checks of BikeTheRail
CheckedResultHandshake
57 minutes agoHandshake completed765 ms
3 days agoHandshake completed44 ms
12 days agoHandshake completed276 ms
13 days agoHandshake completed268 ms
15 days agoHandshake completed312 ms
15 days agoHandshake completed299 ms
17 days agoHandshake completed238 ms
18 days agoHandshake completed298 ms
18 days agoHandshake completed156 ms
20 days agoHandshake completed305 ms
22 days agoHandshake completed194 ms
25 days agoHandshake completed361 ms
27 days agoHandshake completed181 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 BikeTheRail and makes no claim about it beyond what these checks measured.