longwatch.dev
https://longwatch.dev/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 2 whose names suggest state change (create_watch, delete_watch) — 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 | d3c21c298142f128… |
| http_response_observation | 1d ago | 8cc63864dd10634f… |
| availability_observation | 1d ago | 24cdc3bc9c6eaeab… |
| tls_certificate_observation | 1d ago | bd17c60e1b6f96d1… |
| oauth_metadata_observation | 1d ago | 733dd37bc01a206e… |
| mcp_protocol_observation | 1d ago | f864cb269065d82e… |
| mcp_capability_observation | 1d ago | 1b31695d269229d3… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of longwatch.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.