atx/registry

teenadhd.ai/api/mcp/v1

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

71
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1h 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_observation1h ago6cb3fbb04f004b82…
http_response_observation1h ago810e0f8f5a372601…
availability_observation1h ago36d4e1c5e0a86567…
hosting_provider_observation1h agoe7292135d1d3f6bd…
tls_certificate_observation1h ago2adfa0d4a6b89051…
oauth_metadata_observation1h ago5b2181de35146115…
mcp_protocol_observation1h ago9e92c8e66e0aa05d…
mcp_capability_observation1h ago20b1a66307d802e6…

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

Operate this service?

Prove control of teenadhd.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 →