atx/registry

eosl.ai

https://eosl.ai/mcp

57
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
headers.missing_hsts-3
reachable+2

Findings (2)

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 ago09df0f4e57d7066a…
http_response_observation2d ago88e0e6b68aaa0164…
availability_observation2d ago0f561c6b7452ccc4…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago589eff58dd805742…
oauth_metadata_observation2d agoa66bbaca85171b7e…
mcp_protocol_observation2d ago29e201aa088741e0…
mcp_capability_observation2d ago68669358a2f2191a…

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

Operate this service?

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

Claim this profile →