atx/registry

cron.memoryapi.org

https://cron.memoryapi.org/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 (3)

mediumCapabilities are listable without authentication, including 1 whose name suggests state change (cancel_schedule) — 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
dns_resolution_observation2d ago12aef791a4d36667…
http_response_observation2d agob0472c026f877697…
availability_observation2d ago45f21fa41de1c867…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago70636b7ca1ad4397…
oauth_metadata_observation2d ago907d5ea3e391a0cf…
mcp_protocol_observation2d ago8927682e17a4a872…
mcp_capability_observation2d ago1ec6ab20dec35427…

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

Operate this service?

Prove control of cron.memoryapi.org to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →