atx/registry

foodlog.sig.ai/api

https://foodlog.sig.ai/api/mcp

67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h ago

Why this score

mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation3h agoec393937a41578a9…
http_response_observation3h ago1925c82dbc66a6f4…
availability_observation3h ago27a3c2d2c8fe8bc2…
hosting_provider_observation3h ago07b610f7cd67ffa2…
tls_certificate_observation3h ago28ee53b9bc81ce3c…
oauth_metadata_observation3h ago77b7887e7443ab14…
mcp_protocol_observation3h ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →