atx/registry

sighttrue.com/api

https://sighttrue.com/api/mcp

49
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d 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 (3)

mediumCapabilities are listable without authentication, including 2 whose names suggest state change (watch_add, who_can_publish) — 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 (8)

TypeObservedSHA-256
dns_resolution_observation6d agoeab1f9dccd4ec755…
http_response_observation6d ago353bc0cf9623d77a…
availability_observation6d ago2f3b08e6aa04315b…
hosting_provider_observation6d agoe7292135d1d3f6bd…
tls_certificate_observation6d ago1a972fadfd85b857…
oauth_metadata_observation6d agod9bc6b3fd4fb46b5…
mcp_protocol_observation6d ago3fe1cb2f1f429587…
mcp_capability_observation6d agoe1d16f1a225656c1…

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

Operate this service?

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

Claim this profile →