atx/registry

to1-intel.deadbeatradar.workers.dev/mcp/fleet

https://to1-intel.deadbeatradar.workers.dev/mcp/fleet

57
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

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_observation2d ago0fedee8cec5bc2fb…
http_response_observation2d agof97de06ee15203ac…
availability_observation2d agobac4fd020ee7532d…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agoa7c6a02587836bab…
oauth_metadata_observation2d ago8eec68787029779d…
mcp_protocol_observation2d agofdf35231550b168e…
mcp_capability_observation2d ago048cd28e0e4cde27…

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

Operate this service?

Prove control of to1-intel.deadbeatradar.workers.dev/mcp/fleet to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →