Measure.events Analytics MCP Server
io.github.meetclawdius/measure-events
answering
Measure.events Analytics is answering right now. Last checked 7 min ago. It exposes 6 tools.
Privacy-first web analytics. Query pageviews, referrers, trends, and AI insights.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
44 hours of history
44 hours agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
386 ms
Response time
average over 24h
open, no key
Access
streamable-http
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add measure-events --transport http https://lets.measure.events/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"measure-events": {
"url": "https://lets.measure.events/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.measure-events]
url = "https://lets.measure.events/mcp".cursor/mcp.json
{
"mcpServers": {
"measure-events": {
"url": "https://lets.measure.events/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"measure-events": {
"url": "https://lets.measure.events/mcp"
}
}
}Available tools 6
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
site
create_site
Create a new site in Measure.events. Returns the site_key needed for tracking.
get_site_analytics
Get analytics data for a Measure.events site. Returns pageviews, top pages, and referrers for a given period.
get_site_summary
Get a natural language summary of site analytics for the last 7 days, including week-over-week trends.
insights
get_insights
Get proactive insights and anomaly detection for a site — traffic spikes, drops, new referrers.
log
log_checkin
Log agent activity to a site's analytics. Use this to record deployments, content updates, or any agent action on the site.
track
track_event
Track a pageview or event on a site. Use this to instrument agent-driven page visits or actions.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://lets.measure.events/mcp | streamable-http | answering | 421 ms | 7 min ago |
Measure.events Analytics — questions
Answers built from our own checks of this server.
What can Measure.events Analytics do?
It exposes 6 tools, read directly from the server on our last check. Among them: create_site, get_insights, get_site_analytics, get_site_summary, log_checkin, track_event. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Measure.events Analytics working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 386 ms. The bar chart above shows every period we have measured.
Is Measure.events Analytics still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Measure.events Analytics?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Measure.events Analytics need an API key?
No. Measure.events Analytics completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Measure.events Analytics?
It answers our handshake in 386 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.