atx/registry

tlsradar.com/api/v1

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

67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d ago

Why this score

oauth_metadata_present+14
mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (1)

mediumCapabilities are listable without authentication, including 5 whose names suggest state change (add_monitor, add_monitors, create_certificate, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation6d ago1ec16f07df958bca…
http_response_observation6d agoc6515eeb7594d60e…
availability_observation6d ago864bb778bb9af3b3…
hosting_provider_observation6d agoe7292135d1d3f6bd…
tls_certificate_observation6d agoea5520a25186b1b4…
oauth_metadata_observation6d ago34b9b998bd883bed…
mcp_protocol_observation6d ago18f1c627befddd3a…
mcp_capability_observation6d ago163033f85e77ee75…

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

Operate this service?

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

Claim this profile →