atx/registry

api.mcp.ai/p_dietbox

https://api.mcp.ai/p_dietbox

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

mediumCapabilities are listable without authentication, including 12 whose names suggest state change (dietbox_agenda_write, dietbox_anamnese_delete, dietbox_anamnese_write_create, …) — 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 ago648cf4ff284b19b4…
http_response_observation2d agoef7aee9512d5076b…
availability_observation2d ago2ad1ea8f95c0dfee…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago33e8e77911085e24…
oauth_metadata_observation2d agofb6b520679fad340…
mcp_protocol_observation2d ago1532f3f0305e98a1…
mcp_capability_observation2d ago00f2a916c7f482af…

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

Operate this service?

Prove control of api.mcp.ai/p_dietbox to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →