atx/registry

mcp.cdk.bot

https://mcp.cdk.bot/mcp

49
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d 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 4 whose names suggest state change (check_order, confirm_purchase, request_refund, …) — 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_observation2d ago6c4bf9ec677e16eb…
http_response_observation2d ago1278393aae608c53…
availability_observation2d ago6cd013ab4cee0873…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago59931d6bd3a1fc0f…
oauth_metadata_observation2d ago5fc749217493c536…
mcp_protocol_observation2d agof3a487421a42125d…
mcp_capability_observation2d ago5818b9992622b817…

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

Operate this service?

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

Claim this profile →