mcp.standby.design
https://mcp.standby.design/mcp
69
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (2)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | ab88f475a3aa64b9… |
| http_response_observation | 1d ago | d26fad691af57e79… |
| availability_observation | 1d ago | 89f7268eaff1947b… |
| tls_certificate_observation | 1d ago | 7595ecde056d7168… |
| oauth_metadata_observation | 1d ago | 0db0df82df408a19… |
| mcp_protocol_observation | 1d ago | c43fb3b6b2f35cbc… |
| mcp_capability_observation | 1d ago | f9a52cc5f7835f4f… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.standby.design to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.