Remote MCP · Endpoint

Measure.events Analytics MCP server

No. Measure.events Analytics answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lets.measure.events/mcp

The last check completed an MCP handshake.

Registry name
io.github.meetclawdius/measure-events
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Privacy-first web analytics. Query pageviews, referrers, trends, and AI insights.
Listing
From the official MCP registry (active).
Recent checks of Measure.events Analytics
CheckedResultHandshake
1 hour agoHandshake completed298 ms
1 day agoHandshake completed297 ms
2 days agoHandshake completed310 ms
3 days agoHandshake completed295 ms
4 days agoHandshake completed306 ms
5 days agoHandshake completed298 ms
6 days agoHandshake completed295 ms
9 days agoHandshake completed297 ms
11 days agoHandshake completed297 ms
14 days agoHandshake completed58 ms
16 days agoHandshake completed45 ms
18 days agoHandshake completed49 ms
20 days agoHandshake completed54 ms
22 days agoHandshake completed40 ms
24 days agoHandshake completed38 ms
26 days agoHandshake completed86 ms
27 days agoHandshake completed44 ms
29 days agoHandshake completed45 ms

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

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 Measure.events Analytics and makes no claim about it beyond what these checks measured.