JavaScript VM
Related Servers
Alternatives to JavaScript VM
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceProvides a secure, isolated JavaScript execution environment with configurable time and memory limits for safely running code from Claude.15-
- FlicenseNot gradedqualityDmaintenanceEnables secure execution of bash, Python, and Node.js code in isolated Firecracker microVMs with configurable timeouts and no network access.-
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to execute generated Python, Node.js, or shell code inside disposable, network-isolated Docker containers with strict resource, filesystem, privilege, and time limits, returning structured results and errors.MIT
- FlicenseNot gradedqualityDmaintenanceExecutes Python code in isolated subprocesses with resource limits and timeout, designed for safe execution in Docker containers.-
- AlicenseAqualityCmaintenanceEnables AI assistants to securely execute Python and C++ code snippets inside disposable, isolated Docker containers and receive structured results.31MIT
TDQS
Scored across 2 tools
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.
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.
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.
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.