context-relay.contextrelay.workers.dev
https://context-relay.contextrelay.workers.dev/mcp
57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 4h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
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 (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4h ago | 9953983624f72e19… |
| http_response_observation | 4h ago | 894070def113892f… |
| availability_observation | 4h ago | 0cd0d1fad781d500… |
| hosting_provider_observation | 4h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 4h ago | b7c00c0bc193933b… |
| oauth_metadata_observation | 4h ago | 5b3f1a69370b77b3… |
| mcp_protocol_observation | 4h ago | fa63ca6f97a9afb0… |
| mcp_capability_observation | 4h ago | 8cd2b8d8cbb93391… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of context-relay.contextrelay.workers.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.