Skip to main content
Glama

Related Servers

Alternatives to JavaScript VM

No user-submitted related servers found.

    Related Servers

    • 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure cloud-based execution of code across 14+ programming languages within a sandboxed environment. It supports file management, standard input/output handling, and automatic generation of visual artifacts like plots and charts.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Executes Python code in isolated subprocesses with resource limits and timeout, designed for safe execution in Docker containers.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and MCP clients to safely execute and verify multi-language code in a deterministic sandbox, using AST security analysis to block dangerous system calls and capture isolated execution telemetry.
      7
      -

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools are distinguished primarily by language (JavaScript vs TypeScript), which is a clear and predictable selection criterion. However, TypeScript is close to a superset of JavaScript, so a plain JS snippet often runs fine in either tool, leaving a narrow band of genuine overlap.

    Naming Consistency5/5

    Both names follow the same verb_noun snake_case pattern (run_javascript, run_typescript) with a single shared verb and a language noun. The naming is fully predictable and symmetric.

    Tool Count4/5

    Two tools is on the thin side, but the server's scope is narrowly 'execute code in a sandbox,' and one tool per supported language is a defensible, minimal surface. No tool feels redundant or padded.

    Completeness4/5

    Core execution, output capture, error reporting, and fetch are covered, which is the full lifecycle for a stateless code sandbox. Gaps are deliberate constraints rather than omissions: no session/state persistence, no module resolution, no package installation, and no way to pass structured inputs into a run.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues