mcp.doomscore.vc
https://mcp.doomscore.vc/
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 88a36c0510fb72de… |
| http_response_observation | 1d ago | 548851a595c13c60… |
| availability_observation | 1d ago | 062172c7edeb646b… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | f0925df74c43c433… |
| oauth_metadata_observation | 1d ago | 9c289118fac7c1d9… |
| mcp_protocol_observation | 1d ago | 1a6550cc85bc046b… |
| mcp_capability_observation | 1d ago | c5a7d48699a9d471… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.doomscore.vc to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.