atx/registry

catchdoms.com/mcp/catchdoms

https://catchdoms.com/mcp/catchdoms

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

Why this score

mcp_requires_authentication+10
tls_present_and_valid+4
headers.missing_hsts-3
reachable+2

Findings (1)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d ago305c6d39f7e3f63f…
http_response_observation2d ago5af9b22df6f65954…
availability_observation2d agoc09fd02734182ec6…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agob5663c9b665f91b0…
oauth_metadata_observation2d ago01e361556fdbfb55…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →