Skip to main content
Glama
wasmer-sandbox-mcp

wasmer-sandbox-mcp

Related Servers

Alternatives to wasmer-sandbox-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI coding agents to execute shell commands and compile or run code snippets inside sub-6ms hardware-isolated KVM MicroVM sandboxes instead of the local machine. It also lets agents spawn, list, hibernate, wake, and destroy sandboxes — optionally bundled with an embedded PostgreSQL database — behind an SSRF/metadata firewall with Base64-escaped code delivery.
      74
      317 npm
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to run shell commands, spawn persistent background tasks, and read/write files inside isolated remote container sandboxes on a VPS. It also provides project workspace listing, task attach/kill controls, and a searchable knowledge graph for memory continuity across sessions.
      -
    • 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
      The sessionless code interpreter. Securely run AI-generated code in stateful sandboxes that run forever.
      230
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users and LLMs to execute Python code, install packages, run terminal commands, and upload files in isolated Docker containers, returning outputs and HTTP links to generated files through an SSE interface.
      Apache 2.0
    • 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

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools are sharply distinguished (file read/write/list, package install, reset, info). The only potential confusion is run_python vs run_command, since run_command could also invoke Python, but the descriptions draw a clear boundary by directing run_command to non-Python work.

    Naming Consistency5/5

    All eight tools follow a consistent snake_case verb_noun pattern (run_, get_, write_, read_, list_, install_, reset_). The run_ versus sandbox_ prefixes correspond to a meaningful semantic split between execution and sandbox management, so there is no real inconsistency.

    Tool Count5/5

    Eight tools is well within the ideal 3-15 range and maps cleanly to the server's purpose: two executors, three filesystem operations, package installation, state inspection, and reset. Each tool earns its place with no redundant entries.

    Completeness4/5

    The domain — isolated code execution with persistent sandbox state — is well covered: execute, read/write/list files, install packages, inspect, and reset. The only minor gap is the lack of a dedicated file removal tool, but agents can work around it via run_command('rm', ...) or reset_sandbox.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues