mcp.yoku.app
https://mcp.yoku.app/
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 4d1ff21ad2a85884… |
| http_response_observation | 1d ago | f8ec0a155fc89b80… |
| availability_observation | 1d ago | bd94b218d7433928… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | 0955778df70b158b… |
| oauth_metadata_observation | 1d ago | 89d397cb568f40a7… |
| mcp_protocol_observation | 1d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.yoku.app to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.