Measure.events Analytics is an MCP server with 6 tools an agent can call, among them create_site, get_insights, get_site_analytics. It answers at https://lets.measure.events/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Privacy-first web analytics. Query pageviews, referrers, trends, and AI insights.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
create_site | Create a new site in Measure.events. Returns the site_key needed for tracking. Inputs: domain, name |
get_insights | Get proactive insights and anomaly detection for a site — traffic spikes, drops, new referrers. Inputs: site_key |
get_site_analytics | Get analytics data for a Measure.events site. Returns pageviews, top pages, and referrers for a given period. Inputs: site_key, period, from, to |
get_site_summary | Get a natural language summary of site analytics for the last 7 days, including week-over-week trends. Inputs: site_key |
log_checkin | Log agent activity to a site's analytics. Use this to record deployments, content updates, or any agent action on the site. Inputs: site_key, agent, action, note, timestamp |
track_event | Track a pageview or event on a site. Use this to instrument agent-driven page visits or actions. Inputs: site_key, path, referrer, agent, utm_source, utm_medium |
Every block below points at https://lets.measure.events/mcp. Pick your client and copy.
claude mcp add --transport http measure-events-analytics https://lets.measure.events/mcp
{
"mcpServers": {
"measure-events-analytics": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://lets.measure.events/mcp"]
}
}
}{
"mcpServers": {
"measure-events-analytics": {
"url": "https://lets.measure.events/mcp"
}
}
}{
"servers": {
"measure-events-analytics": {
"type": "http",
"url": "https://lets.measure.events/mcp"
}
}
}{
"context_servers": {
"measure-events-analytics": {
"url": "https://lets.measure.events/mcp"
}
}
}{
"mcpServers": {
"measure-events-analytics": {
"serverUrl": "https://lets.measure.events/mcp"
}
}
}{
"mcpServers": {
"measure-events-analytics": {
"url": "https://lets.measure.events/mcp"
}
}
}name: Measure.events Analytics
version: 0.0.1
schema: v1
mcpServers:
- name: Measure.events Analytics
type: streamable-http
url: https://lets.measure.events/mcp{
"mcpServers": {
"measure-events-analytics": {
"httpUrl": "https://lets.measure.events/mcp"
}
}
}{
"mcpServers": {
"measure-events-analytics": {
"type": "http",
"url": "https://lets.measure.events/mcp"
}
}
}{
"mcpServers": {
"measure-events-analytics": {
"url": "https://lets.measure.events/mcp"
}
}
}goose://extension?url=https%3A%2F%2Flets.measure.events%2Fmcp&type=streamable_http&id=measure-events-analytics&name=Measure.events%20Analytics
It answered our last check on 22 October 2026 in 337 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
6, as returned by the server's own tools/list on 17 September 2026: create_site, get_insights, get_site_analytics, get_site_summary, log_checkin, track_event.
It answered our last check on 22 October 2026 in 337 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://lets.measure.events/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.meetclawdius. Endpoint host: lets.measure.events. ARD identifier: urn:air:io.github.meetclawdius:mcp:measure-events.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.