Remote MCP · Endpoint

Rush SR Lap Analyzer MCP server

No. Rush SR Lap Analyzer answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://laps.mcp.rush.sr/mcp

The last check completed an MCP handshake.

Registry name
sr.rush/lap-analyzer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
345 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Analyze AiM RaceStudio lap data: lap times, compare laps, time loss, compare two sessions.
Listing
From the official MCP registry (active).
Recent checks of Rush SR Lap Analyzer
CheckedResultHandshake
1 hour agoHandshake completed345 ms
2 days agoHandshake completed155 ms
4 days agoHandshake completed456 ms
7 days agoHandshake completed215 ms
9 days agoHandshake completed83 ms
11 days agoHandshake completed186 ms
13 days agoHandshake completed144 ms
15 days agoHandshake completed64 ms
16 days agoHandshake completed283 ms
18 days agoHandshake completed193 ms
19 days agoHandshake completed400 ms
20 days agoHandshake completed299 ms
23 days agoHandshake completed188 ms
24 days agoHandshake completed206 ms

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

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