Skip to main content
Glama
vndee

LLM Sandbox

by vndee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to LLM Sandbox

No user-submitted related servers found.

    Related Servers

    • MCP Code Sandbox Server

      chrishayuk
      F
      license
      Not graded
      quality
      D
      maintenance
      An extensible Message Communication Protocol server that provides secure code execution capabilities in isolated sandbox environments, compatible with Claude for Desktop and other MCP clients.
      17
      -

    • Sandbox MCP

      pottekkat
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables LLMs to run ANY code safely in isolated Docker containers.
      122
      MIT

    • Shell-MCP

      kevinwatt
      A
      license
      B
      quality
      D
      maintenance
      A secure MCP server for executing whitelisted shell commands with resource and timeout controls, designed for integration with Claude and other MCP-compatible LLMs.
      20
      389 npm
      7
      MIT

    • cinch-mcp

      yusufkadry
      A
      license
      A
      quality
      D
      maintenance
      MCP server that gives AI assistants a secure gVisor-isolated sandbox to run Python or JavaScript code, returning stdout, stderr, and exit codes without local access.
      1
      16 npm
      MIT

    • mcp-exec

      inhuman
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that executes caller-supplied Python code in a network-isolated, locked-down sandbox and returns stdout/stderr/exit code. Supports stdio, HTTP, and SSE transports with optional auth.
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: execute_code runs code, get_supported_languages lists languages, and get_language_details returns metadata for a specific language. There is no overlap that would cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (execute_code, get_supported_languages, get_language_details). The convention is predictable and readable.

    Tool Count4/5

    Three tools is slightly thin but appropriate for a focused sandbox execution server. Each tool earns its place, though two are lightweight metadata helpers around a single action.

    Completeness4/5

    The surface covers execution and language introspection well. Minor gaps exist, such as file input/output management or execution status/cancellation, but core workflows are supported.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources