oruk.ai
https://oruk.ai/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (2)
| medium | Capabilities are listable without authentication, including 1 whose name suggests state change (oruk_create_trial_key) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | b942069e3b49c34e… |
| http_response_observation | 1d ago | fc8d15d563400951… |
| availability_observation | 1d ago | 5ffac547ae91c217… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | c917212b9432033c… |
| oauth_metadata_observation | 1d ago | f21379829b0c339d… |
| mcp_protocol_observation | 1d ago | 32da32e2693052da… |
| mcp_capability_observation | 1d ago | 53e16566dbfa45c5… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of oruk.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.