atx/registry

zendesk.usefulapi.io

https://zendesk.usefulapi.io/mcp

49
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d 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 (2)

mediumCapabilities are listable without authentication, including 4 whose names suggest state change (zendesk_add_ticket_comment, zendesk_create_ticket, zendesk_execute_view, …) — 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_observation6d agodc88756718038544…
http_response_observation6d ago6fcb5e8fd9d41437…
availability_observation6d agob1b953298bc9be58…
hosting_provider_observation6d agoe7292135d1d3f6bd…
tls_certificate_observation6d ago7f598a0be46c69c7…
oauth_metadata_observation6d ago8c293017a7ae2d61…
mcp_protocol_observation6d agoda3c73fdfa85aaca…
mcp_capability_observation6d agocdcd202fb5c0ab60…

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

Operate this service?

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

Claim this profile →