atx/registry

evlek.app/api

https://evlek.app/api/mcp

61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 4h 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_observation4h ago2af681691683ef02…
http_response_observation4h ago4419b24bc81c497a…
availability_observation4h agoa51f224cf976553a…
hosting_provider_observation4h ago07b610f7cd67ffa2…
tls_certificate_observation4h agofb981b67ff04ff77…
oauth_metadata_observation4h agof274dff281263647…
mcp_protocol_observation4h agoc54eef05e3b37746…
mcp_capability_observation4h ago73202a48aeec55f6…

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

Operate this service?

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

Claim this profile →