atx/registry

mcp.enigma.com/http-key

https://mcp.enigma.com/http-key

89
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d ago

Why this score

oauth_metadata_present+14
tls_present_and_valid+12
mcp_requires_authentication+10
reachable+6
headers.missing_hsts-3

Findings (1)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (6)

TypeObservedSHA-256
dns_resolution_observation1d ago9b4a56603dd21f88…
http_response_observation1d ago5d8e3eac5d31daa7…
availability_observation1d agofe1830aeb7683396…
tls_certificate_observation1d ago3522be28f443b6bd…
oauth_metadata_observation1d ago790ef708b3a8c161…
mcp_protocol_observation1d ago5f4c66c82509bed4…

Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.

Operate this service?

Prove control of mcp.enigma.com/http-key to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →