mcp.ecoa.dev/api/mcp/public
https://mcp.ecoa.dev/api/mcp/public
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | b6e6a00c62fed3d2… |
| http_response_observation | 1d ago | 845f271215eb075f… |
| availability_observation | 1d ago | fcb22196188dd3bd… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | b55f4a12a08128ad… |
| oauth_metadata_observation | 1d ago | eb528220b77e678d… |
| mcp_protocol_observation | 1d ago | 8f12ddc4ea8e259c… |
| mcp_capability_observation | 1d ago | 29e6c3ee0a4a8a16… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.ecoa.dev/api/mcp/public to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.