lets.measure.events
https://lets.measure.events/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (2)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (create_site) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | de624c6618247ddf… |
| http_response_observation | 1d ago | 8422b5892dacafb5… |
| availability_observation | 1d ago | 3e6a3ad9aa3e7fac… |
| tls_certificate_observation | 1d ago | 04af0882dd35db04… |
| oauth_metadata_observation | 1d ago | 99ced27cf073308a… |
| mcp_protocol_observation | 1d ago | 44a1e627263442fa… |
| mcp_capability_observation | 1d ago | 2e9ecf4def9ceb90… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of lets.measure.events to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.