churnlens.site/api
https://churnlens.site/api/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1h ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1h ago | d4202eb464dce60b… |
| http_response_observation | 1h ago | b5377d3cf53a6000… |
| availability_observation | 1h ago | ae6a4c2cec91e031… |
| hosting_provider_observation | 1h ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 1h ago | 1e35de2ce69c635b… |
| oauth_metadata_observation | 1h ago | d997e258b468f5b3… |
| mcp_protocol_observation | 1h ago | 661ad8f032d72f32… |
| mcp_capability_observation | 1h ago | 26f1ca0929a21b16… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of churnlens.site/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.