huggingface.co
https://huggingface.co/mcp
83
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 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| 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 (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 1e1024d133dc3694… |
| http_response_observation | 2d ago | 66e11a58f127b51a… |
| availability_observation | 2d ago | c0d1f7ae41f47935… |
| tls_certificate_observation | 2d ago | d29fdb9fbb5fcc9b… |
| oauth_metadata_observation | 2d ago | 8f063ad84f7c37ee… |
| mcp_protocol_observation | 2d ago | 0067b56449b08ba8… |
| mcp_capability_observation | 2d ago | 1d6901f9c6c96d0e… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of huggingface.co to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.