atx/registry

childadhd.ai/api/mcp/v1

https://childadhd.ai/api/mcp/v1

71
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2h ago

Why this score

oauth_metadata_present+14
tls_present_and_valid+4
mcp_capabilities_discoverable+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 (8)

TypeObservedSHA-256
dns_resolution_observation2h ago4c0d19cd719ec2be…
http_response_observation2h ago74ff9b4f57abca89…
availability_observation2h ago239390857fdc02e4…
hosting_provider_observation2h agoe7292135d1d3f6bd…
tls_certificate_observation2h ago8faed720f6222191…
oauth_metadata_observation2h agoa3e41528f62810ff…
mcp_protocol_observation2h ago2f53c9152a4ea717…
mcp_capability_observation2h agob7f1c11de7a7a2cc…

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

Operate this service?

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

Claim this profile →