atx/registry

cdbx.ai/api/mcp/server

https://cdbx.ai/api/mcp/server

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1h ago

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation1h agof02f9ee7b7a3b011…
http_response_observation1h ago2d24a54ac868ec92…
availability_observation1h ago3d8e818e7a872d3f…
hosting_provider_observation1h agoe7292135d1d3f6bd…
tls_certificate_observation1h ago0786c076fbece18f…
oauth_metadata_observation1h ago5063a01160d2e98c…
mcp_protocol_observation1h ago5f4c66c82509bed4…

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

Operate this service?

Prove control of cdbx.ai/api/mcp/server to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →