atx/registry

cronofy.usefulapi.io

https://cronofy.usefulapi.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 (cronofy_delete_event) — 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
tls_certificate_observation2d ago9f264d7307909077…
dns_resolution_observation2d agof035bc2f10a1fb81…
http_response_observation2d ago496162a5fd517ef4…
availability_observation2d ago6ff7389160e7ff34…
hosting_provider_observation2d agoe7292135d1d3f6bd…
oauth_metadata_observation2d agoebc3a49b7142a1eb…
mcp_protocol_observation2d ago54a1c92ff36f6b6a…
mcp_capability_observation2d ago9f1e62e66f0d29d3…

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

Operate this service?

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

Claim this profile →