mcp.beket.ai/registry
https://mcp.beket.ai/registry/mcp
77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 17h ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 17h ago | 82c91c302216159b… |
| http_response_observation | 17h ago | 4ce6ac985cae4c27… |
| availability_observation | 17h ago | 4a445ca9d2a1f0a8… |
| hosting_provider_observation | 17h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 17h ago | 258dba048a546ab0… |
| oauth_metadata_observation | 17h ago | ca70200ce6660fbf… |
| mcp_protocol_observation | 17h ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.beket.ai/registry to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.