mcp.reka.ai
https://mcp.reka.ai/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (2)
| medium | Capabilities are listable without authentication, including 5 whose names suggest state change (create_group, delete_group, delete_video, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 7f437877e0b09742… |
| http_response_observation | 2d ago | 4ebdf264f52b1a11… |
| availability_observation | 2d ago | b71ae33ff9600538… |
| tls_certificate_observation | 2d ago | ffd044186c45aa52… |
| oauth_metadata_observation | 2d ago | 7ac02e170fdf48c4… |
| mcp_protocol_observation | 2d ago | 91bbaccaa6e5878a… |
| mcp_capability_observation | 2d ago | 9fe29610ca688003… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.reka.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.