A
licenseNot graded
qualityC
maintenanceAn MCP server to create secure code sandbox environment for executing code within Docker containers.
327
MIT
mcp_oi_assistant
by Stellinora
Related Servers
Alternatives to mcp_oi_assistant
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for copying and pasting code between files with security controls and validation.5MIT
- AlicenseAqualityCmaintenanceSecurity-hardened MCP server that runs only allowlisted commands with no shell, jailed to a single directory, and bounded execution.2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that runs a quality gate on generated code, executing it in a sandbox and scoring it before returning the code to the user.5 npmMIT
- FlicenseAqualityDmaintenanceAn MCP server for ROS 2 development that enables controlled creation of workspaces, packages, nodes, launch files, and tests within a sandboxed directory, with secure filesystem boundaries.8-
- AlicenseBqualityBmaintenanceThis MCP server enables MCP clients such as Claude Desktop to run LLM-generated code in a secure, isolated sandbox across multiple container backends and programming languages.23113,139 PyPI1,143MIT
TDQS
B3.2/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a distinct operation: compiling/running code, debugging with GDB, comparing outputs, reading a test case, and inspecting environment state. There is no meaningful overlap between these purposes, so an agent can select the right tool without confusion.
Naming Consistency4/5
All names use snake_case and are action-oriented, mostly following a verb_noun pattern such as compare_outputs, read_test_case, and get_environment_info. Minor deviations like compile_and_run and debug_with_gdb introduce conjunction/preposition forms, but the overall convention remains predictable.
Tool Count5/5
Five tools is well-scoped for a C++ olympiad-style assistant: compile/run, debug, compare outputs, read test cases, and check the toolchain environment. Each tool has a clear role, with no obvious filler or missing core capability at this scope.
Completeness4/5
The surface covers the core compile-run-debug-test workflow, including test case reading, output comparison, and environment inspection. Minor gaps remain, such as writing/editing source files, listing available test cases, or running a batch of test cases, but these can likely be handled outside this server.