atx/registry

journalize.dev

https://journalize.dev/mcp

49
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h ago

Why this score

mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
headers.missing_hsts-3
reachable+2

Findings (2)

mediumCapabilities are listable without authentication, including 2 whose names suggest state change (submit_batch, submit_directive) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation3h agod778f81449f61c85…
http_response_observation3h agofa546ad903710854…
availability_observation3h ago5840f968a8e65206…
hosting_provider_observation3h agoe7292135d1d3f6bd…
tls_certificate_observation3h ago7592d1b93138b11b…
oauth_metadata_observation3h agod090559c13184074…
mcp_protocol_observation3h ago6c1ddb2344b96328…
mcp_capability_observation3h ago74eea2feb1c42b79…

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

Operate this service?

Prove control of journalize.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →