atx/registry

api.storyflo.com/mcp/v1

https://api.storyflo.com/mcp/v1

75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago

Why this score

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

Findings (2)

mediumCapabilities are listable without authentication, including 4 whose names suggest state change (fm_close_position, publisher_upload_audio, subscribe_declassified_topic, …) — 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 (7)

TypeObservedSHA-256
dns_resolution_observation2d agodb90047b10fbe814…
http_response_observation2d agof1a7fc5f15162624…
availability_observation2d agoc0edb4c5a0f6291b…
tls_certificate_observation2d ago536154b477f5f7e5…
oauth_metadata_observation2d ago29344ecf84d4fd1c…
mcp_protocol_observation2d ago9dd54ca2469dc9a9…
mcp_capability_observation2d ago1342bde02d7b8bfe…

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

Operate this service?

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

Claim this profile →