atx/registry

mnemolog.com/api

https://mnemolog.com/api/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago

Why this score

mcp_requires_authentication+10
tls_present_and_valid+4
headers.missing_hsts-3
reachable+2

Findings (2)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation1d agoc7e7f849bd4f464e…
http_response_observation1d ago65b910df63d6d4fd…
availability_observation1d agob5b9f229b7953211…
hosting_provider_observation1d agoe7292135d1d3f6bd…
tls_certificate_observation1d ago477cce1ba9b134cd…
oauth_metadata_observation1d agoa66d01f597ac0ac8…
mcp_protocol_observation1d ago5f4c66c82509bed4…

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

Operate this service?

Prove control of mnemolog.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →