Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Measure.events Analytics

REMOTE · LETS.MEASURE.EVENTS · SCANNED AUG 3

Privacy-first web analytics. Query pageviews, referrers, trends, and AI insights.

+4 this week 62 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 471 tokens (~78/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · lets.measure.events

# add to Claude Code
claude mcp add --transport http meetclawdius-measure-events https://lets.measure.events/mcp
# ~/.codex/config.toml
[mcp_servers.meetclawdius-measure-events]
url = "https://lets.measure.events/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "meetclawdius-measure-events": {
      "type": "remote",
      "url": "https://lets.measure.events/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add meetclawdius-measure-events --url https://lets.measure.events/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  meetclawdius-measure-events:
    url: "https://lets.measure.events/mcp"
// mcp.json
{
  "mcpServers": {
    "meetclawdius-measure-events": {
      "type": "http",
      "url": "https://lets.measure.events/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 58

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://lets.measure.events/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lets.measure.events CN=YE1,O=Let's Encrypt,C=US 23 Jul 2026 21 Oct 2026 ECDSA 256 ECDSA-SHA384 5691c909c7ed0d94ba5374e0015b65007a2
SANs: lets.measure.events
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of lets.measure.events. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
events. present 12487 8 Verified
measure.events. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://lets.measure.events/mcp Verified 200
http (plaintext) http://lets.measure.events/mcp HTTPS enforced 308 https://lets.measure.events/mcp
MCP tools — 6 exposed · ~431 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
create_site ~51

Create a new site in Measure.events. Returns the site_key needed for tracking.

NameTypeReqDescription
domainstringyesThe site's domain (e.g. example.com)
namestringyesHuman-readable site name

No output schema declared.

No examples provided.

get_insights ~41

Get proactive insights and anomaly detection for a site — traffic spikes, drops, new referrers.

NameTypeReqDescription
site_keystringyesThe site's tracking ID

No output schema declared.

No examples provided.

get_site_analytics ~95

Get analytics data for a Measure.events site. Returns pageviews, top pages, and referrers for a given period.

NameTypeReqDescription
fromstringStart date YYYY-MM-DD (for custom range)
periodstringTime period (default: month)
site_keystringyesThe site's tracking ID (site_key)
tostringEnd date YYYY-MM-DD (for custom range)

No output schema declared.

No examples provided.

get_site_summary ~42

Get a natural language summary of site analytics for the last 7 days, including week-over-week trends.

NameTypeReqDescription
site_keystringyesThe site's tracking ID

No output schema declared.

No examples provided.

log_checkin ~97

Log agent activity to a site's analytics. Use this to record deployments, content updates, or any agent action on the site.

NameTypeReqDescription
actionstringyesWhat the agent did (e.g. 'published article')
agentstringAgent name
notestringAdditional context
site_keystringyesThe site's tracking ID
timestampstringISO8601 timestamp (defaults to now)

No output schema declared.

No examples provided.

track_event ~105

Track a pageview or event on a site. Use this to instrument agent-driven page visits or actions.

NameTypeReqDescription
agentstringAgent name for attribution
pathstringyesPage path (e.g. /about)
referrerstringReferring URL
site_keystringyesThe site's tracking ID
utm_campaignstring
utm_mediumstring
utm_sourcestring

No output schema declared.

No examples provided.