atx/registry

api.e2a.dev

https://api.e2a.dev/mcp

77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2h ago

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+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 (7)

TypeObservedSHA-256
dns_resolution_observation2h ago502be63bfe177ba4…
http_response_observation2h ago213d7632616cd8e2…
availability_observation2h agodc5797acb2fa1e3c…
hosting_provider_observation2h agoe7292135d1d3f6bd…
tls_certificate_observation2h ago1e552f9c1d48ef5f…
oauth_metadata_observation2h ago9dcc50da94e750dd…
mcp_protocol_observation2h ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →