Skip to main content
Glama
AbhiteshPundir

Sandbox MCP

by AbhiteshPundir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Sandbox MCP

No user-submitted related servers found.

    Related Servers

    • Sandbox MCP

      Dhananjay-JSR
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute commands, run tests, and modify project files inside disposable, policy-enforced Docker sandboxes that are isolated from the host machine and its credentials.
      15
      MIT

    • Sandbox MCP

      riyasaxena32
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute code, run tests, and build projects inside disposable Docker sandboxes, protecting the host machine through enforced isolation, filesystem snapshots, and network controls.
      15
      MIT

    • Secure Grid Genesis Execution

      Coraje187
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely execute Python, JavaScript, and Bash code in an isolated Docker sandbox with strict security constraints.
      1
      -

    • Advanced MCP Server

      Nom-nom-hub
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with a secure, sandboxed environment for executing coding tasks including file operations, command execution, and testing. Features session management, policy enforcement, and Docker-based sandboxing for safe code execution and development workflows.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose, and descriptions explicitly state when to use each one, such as run_tests versus execute_experiment for test-specific vs general commands. There is no meaningful overlap or ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: create_experiment, read_sandbox_file, get_job_result, etc. While some verbs like 'run' and 'execute' are synonymous, they apply to different objects (tests vs experiments) and the overall pattern is uniform.

    Tool Count5/5

    With 15 tools, this server sits at the upper bound of the ideal 3-15 range, but each tool serves a distinct and necessary function in the sandbox lifecycle, from creation to destruction, file manipulation, job management, and comparison. No tool feels redundant or extraneous.

    Completeness4/5

    The tool surface covers the full experiment lifecycle and core workflows: create, inspect, execute, collect, compare, and destroy. The only minor gap is the lack of a directory-listing or file-discovery tool inside the sandbox, requiring agents to shell out via execute_experiment to explore the filesystem.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources