atx/registry

api.synlake.ai/api

https://api.synlake.ai/api/mcp

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d agof11d978592d14d53…
http_response_observation2d ago03f15ee3ad169431…
availability_observation2d ago4cc2f2d82bcb1189…
hosting_provider_observation2d ago07b610f7cd67ffa2…
tls_certificate_observation2d agoa765c8da0a80f11d…
oauth_metadata_observation2d ago1c480d37dd7b97bd…
mcp_protocol_observation2d ago9475ae7f2ccf4b8f…
mcp_capability_observation2d ago3070f1625417370b…

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

Operate this service?

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

Claim this profile →