atx/registry

mcp.pictify.io

https://mcp.pictify.io/

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

Why this score

oauth_metadata_present+14
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 8 whose names suggest state change (pictify_cancel_batch, pictify_create_canvas_image, pictify_create_gif, …) — 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
availability_observation2d agod7c4275cbdca5a4e…
dns_resolution_observation2d ago32958a7985963af2…
http_response_observation2d ago51c56b947e25381f…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago35585102ab5a425b…
oauth_metadata_observation2d agoe350742e02a4d8b0…
mcp_protocol_observation2d ago19eb8d02090a0b12…
mcp_capability_observation2d ago5a69773237662a96…

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

Operate this service?

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

Claim this profile →