Skip to main content
Glama
riyasaxena32

Sandbox MCP

by riyasaxena32
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

      AbhiteshPundir
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely run commands, install dependencies, test, and modify code inside disposable, policy-enforced Docker sandboxes isolated from the host, returning results and diffs.
      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.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes, but get_job_status and get_job_result could be confused from names alone, and execute_experiment vs run_tests require careful reading. Descriptions do clarify the boundaries.

    Naming Consistency4/5

    All names follow verb_noun with underscores, but the set mixes 'job' for command execution and 'experiment' for sandbox lifecycle, creating slight inconsistency. Overall pattern is still predictable.

    Tool Count4/5

    15 tools is on the higher end but each covers a distinct sandbox operation: lifecycle, execution, file access, change tracking, artifacts, and comparison. No obvious redundancy, though a few could be consolidated.

    Completeness5/5

    The tool surface covers the full experiment workflow: create, execute, test, read/write files, inspect changes, collect artifacts, compare, and destroy. It deliberately omits host modification, which fits the sandbox safety model.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources