{"id":"sandboxrunner-mcp-server","name":"mcp-server","af_score":42.5,"security_score":35.0,"reliability_score":21.2,"what_it_does":"An MCP (Model Context Protocol) server that runs user-provided code inside isolated, resource-limited sandbox environments using runc/OCI containers. It supports multiple programming languages via language-specific handlers and offers persistence for sandbox state via SQLite. It can expose MCP over stdio or HTTP/WebSocket and includes configurable security policies and audit logging.","best_when":"When you need an agent-accessible, multi-language execution sandbox that isolates processes via OCI containers and you can deploy on Linux with container support.","avoid_when":"When you cannot enforce/verify network, filesystem, and container escape protections beyond what is documented, or when you need first-class enterprise auth, documented rate limiting, and strong API error/retry semantics.","last_evaluated":"2026-04-04T21:22:22.128337+00:00","has_mcp":true,"has_api":true,"auth_methods":[],"has_free_tier":false,"known_gotchas":["Sandboxed execution commonly has limits (CPU/memory/disk) that may cause failures; agents should be prepared to handle execution timeouts/OOM/disk-full conditions.","When using container-based runners, agents may need to explicitly provide all dependencies/source in the request; “import/package availability” may differ from the agent’s environment.","If MCP is exposed over HTTP/WebSocket, ensure transport/auth/network isolation is configured appropriately; the README does not document auth details.","State persistence via SQLite may require cleanup/retention policies to avoid unintended cross-run state or storage growth."],"error_quality":0.0}