Skip to main content
Glama
gradion-ai

ipybox

by gradion-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to ipybox

No user-submitted related servers found.

    Related Servers

    • Sandbox MCP

      AbhiteshPundir
      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

    • Python MCP Sandbox

      JohanLi233
      A
      license
      Not graded
      quality
      D
      maintenance
      An interactive Python code execution environment that allows users and LLMs to safely execute Python code and install packages in isolated Docker containers.
      40
      Apache 2.0

    • Sandbox Agent

      eduresser
      A
      license
      A
      quality
      C
      maintenance
      Enables code execution in isolated Docker containers with persistent IPython, Node.js, or R kernels, supporting file import/export and cross-session transfers via MCP tools.
      6
      MIT

    • Docker MCP Server

      cevatkerim
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to safely execute code in isolated Docker containers with resource limits and security controls, supporting session management and automatic dependency installation.
      MIT

    • MCP Executor Server

      nikhilkumaragarwal-shyftlabs
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A secure server that enables code execution in isolated Docker environments, supporting Python with strict security constraints including network isolation, limited filesystem access, and resource limitations.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: download_file retrieves files from container to host, execute_ipython_cell runs Python code in a persistent kernel, reset clears kernel state, and upload_file sends files from host to container. The boundaries are unambiguous, preventing agent misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (download_file, execute_ipython_cell, reset, upload_file) with clear, descriptive actions. Reset is a single verb but fits naturally as it describes a clear action without needing a noun, maintaining overall consistency in style and readability.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of interactive Python execution in a container. Each tool earns its place by covering essential operations: file transfer (upload/download), code execution, and state management (reset). This count avoids bloat while providing complete workflow coverage.

    Completeness5/5

    The tool set provides complete coverage for the domain of container-based IPython execution. It supports the full lifecycle: uploading files, executing code with state persistence, resetting the environment, and downloading results. No obvious gaps exist; agents can perform end-to-end workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources