zerm.dev
https://zerm.dev/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d 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 5 whose names suggest state change (inbox_create, inbox_delete, kv_delete, …) — 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 | 6d ago | bb2ca791a8bf0c42… |
| http_response_observation | 6d ago | c96c94bd3f9ee3d5… |
| availability_observation | 6d ago | a63482f58834212f… |
| tls_certificate_observation | 6d ago | bb1fb790b81f116d… |
| oauth_metadata_observation | 6d ago | d93f72e37ac947a1… |
| mcp_protocol_observation | 6d ago | 2be4d603f6a2e96a… |
| mcp_capability_observation | 6d ago | cb7eb5da63e79ac7… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of zerm.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.