Remote MCP · Endpoint

Rail Crossing Atlas MCP server

No. Rail Crossing Atlas answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://railcrossingatlas.tansolutions.org/mcp

The last check completed an MCP handshake.

Registry name
org.tansolutions.railcrossingatlas/crossings
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
896 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Look up US railroad crossings: equipment, daily trains, road traffic, county and state summaries.
Listing
From the official MCP registry (active).
Recent checks of Rail Crossing Atlas
CheckedResultHandshake
1 hour agoHandshake completed896 ms
3 days agoHandshake completed926 ms
13 days agoHandshake completed848 ms
14 days agoHandshake completed887 ms
15 days agoHandshake completed1.44 s
16 days agoHandshake completed311 ms
18 days agoHandshake completed813 ms
18 days agoHandshake completed855 ms
19 days agoHandshake completed832 ms
21 days agoHandshake completed882 ms
22 days agoHandshake completed879 ms
25 days agoHandshake completed885 ms
27 days agoHandshake completed794 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 Rail Crossing Atlas and makes no claim about it beyond what these checks measured.