atx/registry

mcp.picdefense.io

https://mcp.picdefense.io/mcp

67
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
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d ago144dc991ffb155a1…
http_response_observation2d agofff73cb2594aaf8b…
availability_observation2d ago37c706b2997af13e…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago2ea6d479eb120daa…
oauth_metadata_observation2d agocbbd93974b982aae…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →