Remote MCP · Endpoint

livedot MCP MCP server

No. livedot MCP answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://livedot.me/mcp

The last check completed an MCP handshake.

Registry name
me.livedot/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
197 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find someone in a live running or cycling race, clubs and coaches near you, and race-day weather.
Listing
From the official MCP registry (active).
Recent checks of livedot MCP
CheckedResultHandshake
34 minutes agoHandshake completed197 ms
9 days agoHandshake completed225 ms
10 days agoHandshake completed293 ms
11 days agoHandshake completed233 ms
12 days agoHandshake completed224 ms
14 days agoHandshake completed280 ms
14 days agoHandshake completed206 ms
15 days agoHandshake completed203 ms
17 days agoHandshake completed466 ms
19 days agoHandshake completed335 ms
21 days agoHandshake completed103 ms
24 days agoHandshake completed140 ms
26 days agoHandshake completed178 ms
28 days agoHandshake completed66 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 livedot MCP and makes no claim about it beyond what these checks measured.