{"id":"ramibotai-ramibot","name":"ramibot","af_score":33.5,"security_score":39.8,"reliability_score":28.8,"what_it_does":"RamiBot is a self-hosted, local-first AI security operations chat application that integrates multiple LLM providers with an MCP-powered security-tool pipeline. It runs security tooling inside Docker (including a dedicated rami-kali MCP server), supports Tor proxy routing, maintains local SQLite conversation/history, gates tool execution with a human-in-the-loop approval step, and enforces evidence-locked reporting to reduce fabricated findings.","best_when":"You want a self-hosted, operator-controlled environment that connects LLM reasoning to real security tools with evidence-focused output and explicit approval for tool execution.","avoid_when":"You need a turnkey, cloud-hosted service with minimal local infrastructure/security review, or you require a mature, clearly specified developer API (OpenAPI/SDK) for agent integration.","last_evaluated":"2026-03-30T15:37:52.884988+00:00","has_mcp":true,"has_api":true,"auth_methods":["Configured provider API keys in backend settings.json (e.g., OpenAI; Anthropic noted as pending re-enablement)"],"has_free_tier":false,"known_gotchas":["Human approval gate: agents must handle waiting for operator approval (timeout/auto-deny behavior).","Tool calls may be blocked until approval; agent should not assume immediate execution.","Evidence-locked reporting may constrain agent output; it must rely on evidence blocks rather than model guesses.","Docker/Tor/proxy routing features require environment setup and may affect tool accessibility and timing."],"error_quality":0.0}