auth.echoai.so/functions/v1
https://auth.echoai.so/functions/v1/mcp
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 7d ago
Why this score
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 7d ago | 88af0deedfa9a7b2… |
| http_response_observation | 7d ago | 2ef7b47ffb663ec3… |
| availability_observation | 7d ago | 46788f981f0246ac… |
| hosting_provider_observation | 7d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 7d ago | 1deecd108f11432b… |
| oauth_metadata_observation | 7d ago | a18567b41031296c… |
| mcp_protocol_observation | 7d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of auth.echoai.so/functions/v1 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.