atx/registry

api.picsee.io

https://api.picsee.io/mcp

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 (2)

mediumCapabilities are listable without authentication, including 1 whose name suggests state change (create_short_link) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d agodf3943e37e588d2a…
http_response_observation2d agocea1589a89e0a156…
availability_observation2d ago513fc73f80f3223f…
hosting_provider_observation2d agoe0cc952cc06f53e3…
tls_certificate_observation2d agof826194243a33a27…
oauth_metadata_observation2d ago356393e1d070b595…
mcp_protocol_observation2d ago776a1a8fdf998b98…
mcp_capability_observation2d ago530d21b7ddf2f944…

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

Operate this service?

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

Claim this profile →