mcp.hackle.io
https://mcp.hackle.io/mcp
89
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| mcp_requires_authentication | +10 |
| reachable | +6 |
| 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 (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 31942bb6cc9f56d9… |
| http_response_observation | 2d ago | 4a1ec8e057e09df9… |
| availability_observation | 2d ago | db15e575f50dd6f9… |
| tls_certificate_observation | 2d ago | 9c00bafcaf7f9584… |
| oauth_metadata_observation | 2d ago | 71849c5ef9d6d033… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.hackle.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.