getyo.dev
https://getyo.dev/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | Capabilities are listable without authentication, including 2 whose names suggest state change (cancel_registration, revoke_self) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 3h ago | f76432cf14dcd837… |
| http_response_observation | 3h ago | f0b2c44b7c2335ce… |
| availability_observation | 3h ago | b7a867d08c4835e7… |
| hosting_provider_observation | 3h ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 3h ago | f77a1e78d0102e4e… |
| oauth_metadata_observation | 3h ago | ea3c6fbc81227574… |
| mcp_protocol_observation | 3h ago | d09d69c6f50fb0dc… |
| mcp_capability_observation | 3h ago | 434bfe60078fa85a… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of getyo.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.