F
licenseA
qualityC
maintenanceA secure, containerized workspace for LLMs to autonomously code, test, and debug projects without risking the host machine.
6
1
-
Local Sandbox MCP Environment
Related Servers
Alternatives to Local Sandbox MCP Environment
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides a secure, containerized Python sandbox for executing LLM-generated code with multi-layer isolation, along with JSON/CSV validation and workspace state snapshots.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with local Python environments, execute code and scripts, manage packages, and read or write files within an isolated working directory.-
- AlicenseNot gradedqualityBmaintenanceProvides a restricted Docker-based sandbox for LLM agents, enabling file operations, command execution, and local Git within an isolated runtime.24 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to understand, run, test, diagnose, review, benchmark, and validate real local software projects through the Model Context Protocol. It provides workspace-confined safe execution, structured evidence instead of raw logs, and Git checkpoints with guarded rollback that never destroys user work.3 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to manage Python environments, execute code and scripts, install packages, and read or write files within an isolated working directory.-
TDQS
A3.6/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a clearly distinct resource and action: file CRUD, Python execution, and read-only database access are cleanly separated. The only adjacent pair, describe_schema and query_db, is well differentiated by one returning metadata and the other returning query results.
Naming Consistency5/5
All six tools follow a consistent snake_case verb_noun pattern (run_python, describe_schema, query_db, list_files, write_file, read_file). No mixed conventions or vague verbs.
Tool Count5/5
Six tools is a tight, well-scoped surface for a sandbox environment; every tool earns its place with no redundancy. Nothing feels padded or thin.
Completeness4/5
File read/write/list, code execution, and DB inspection cover the core sandbox workflow, but there is no delete_file or directory-creation operation, which agents may need when cleaning up or organizing the workspace. A way to pass arguments/stdin to run_python is also absent but workable.
Maintenance
ActivityMaintained
ResponsivenessNo issues