api.justhappened.wtf
https://api.justhappened.wtf/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | dd36d680a8af9f23… |
| http_response_observation | 2d ago | 53c3e217d1f89ada… |
| availability_observation | 2d ago | aec7765788382de3… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 4632cf458eb44cd1… |
| oauth_metadata_observation | 2d ago | 9a3c24dc7031e190… |
| mcp_protocol_observation | 2d ago | a3753f20b591517d… |
| mcp_capability_observation | 2d ago | 0e3cad3dee09df1c… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.justhappened.wtf to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.