atx/registry

susurration.ai

https://susurration.ai/mcp

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

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

Findings (3)

mediumCapabilities are listable without authentication, including 4 whose names suggest state change (flock_create, flock_create_from_trace, flock_set_params, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
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_observation2d ago5fc32e29e9a3e38d…
http_response_observation2d ago4e1ac43f47c09f91…
availability_observation2d ago11c2f6c2395ad191…
tls_certificate_observation2d agobc5abf41c49b3bb1…
oauth_metadata_observation2d ago34f98868f06ca74f…
mcp_protocol_observation2d ago4d7efb16d7f99595…
mcp_capability_observation2d ago2e26431b04ed9545…

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

Operate this service?

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

Claim this profile →