eodly.io/api
https://eodly.io/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)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 119fc89b30e707fc… |
| http_response_observation | 2d ago | f25681be1914a299… |
| availability_observation | 2d ago | 726fded1b8004e25… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | f68a656fbd91f345… |
| oauth_metadata_observation | 2d ago | 7b2f9d52004ea866… |
| mcp_protocol_observation | 2d ago | 2d0309e09249776e… |
| mcp_capability_observation | 2d ago | 91505b9a1b0b4314… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of eodly.io/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.