Skip to main content
Glama
garc33

JavaScript Sandbox MCP Server

by garc33

Related Servers

Alternatives to JavaScript Sandbox MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides secure execution of arbitrary JavaScript code within a sandboxed QuickJS WASM environment, allowing language models or other MCP clients to safely run JavaScript code snippets without compromising the host system.
      4
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables executing submitted code snippets in a fresh isolated V8 isolate, capturing stdout, stderr, return values, and failures under enforced resource limits.
      2
      Apache 2.0
    • A
      license
      A
      quality
      F
      maintenance
      A secure JavaScript REPL server that enables executing code snippets in a sandboxed environment with memory protection, timeout handling, and comprehensive error reporting.
      1
      11 npm
      120
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables secure execution of bash, Python, and Node.js code in isolated Firecracker microVMs with configurable timeouts and no network access.
      -
    • 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides sandboxed code execution for AI agents with support for Python, JavaScript, and shell commands. Includes comprehensive safety features like destructive pattern blocking, timeout protection, and restricted file access for secure production use.
      16 npm
      89 PyPI
      MIT

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as executing JavaScript code in isolation, making it distinct by default.

    Naming Consistency5/5

    The single tool name 'execute_js' follows a clear verb_noun pattern (execute + js). Since there is only one tool, consistency is inherently perfect with no deviations to assess.

    Tool Count2/5

    A single tool is too few for a server named 'JavaScript Sandbox MCP Server', which implies broader functionality like evaluating expressions, managing contexts, or handling errors. This minimal set feels thin and under-scoped for the apparent domain.

    Completeness2/5

    The tool surface is severely incomplete for a JavaScript sandbox domain. It lacks essential operations such as evaluating expressions, clearing contexts, handling errors, or managing state, which are typical for such environments, leading to significant gaps in functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues