api.contextcloud.pro/mcp/protocol
https://api.contextcloud.pro/mcp/protocol
77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2h ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +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 (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2h ago | 5eb45d803b7666ab… |
| http_response_observation | 2h ago | 87392815f5e5f9c3… |
| availability_observation | 2h ago | 1f61f8b66201a1a9… |
| hosting_provider_observation | 2h ago | f6ca63562d443d49… |
| tls_certificate_observation | 2h ago | 09a6789a51368f9a… |
| oauth_metadata_observation | 2h ago | 460cb5e32575fc42… |
| mcp_protocol_observation | 2h ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.contextcloud.pro/mcp/protocol to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.