Skip to main content
Glama
Boredem125

sandbox

by Boredem125
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sandbox

No user-submitted related servers found.

    Related Servers

    • @looppause/mcp

      soteeabam
      A
      license
      Not graded
      quality
      D
      maintenance
      Pauses AI agent execution and routes approval requests to humans via Slack or email, with cryptographically signed proof of the human's decision.
      17 npm
      MIT
    • @quirna/mcp by quirna

      @quirna/mcpofficial

      quirna
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to request human approval before consequential actions, with policy-based routing, phone-based approver decisions, and signed audit evidence.
      20 npm
      MIT

    • Approval Gate

      Keldrik
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a human approval gate for AI agents, enabling interactive inline cards for approving, editing, or rejecting actions before they are executed.
      MIT

    • genpark-agent-human-in-the

      Alpha-Park
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous agents and multi-agent frameworks to route actions through deterministic human approval gates before execution. Enforces risk tiers, reversible checkpoints, and token approval bounds so that risky or costly operations can be reviewed, bounded, and rolled back without LLM round-trips.
      7
      -

    • stillvault-mcp

      Wolstapp
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to securely use real secrets (API keys, database passwords) by requiring human approval for each release, ensuring secrets never enter the model's context.
      2
      Apache 2.0
    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/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct capability: shell execution, file access, network fetch, request status, and sandbox overview. There is no overlap in purpose, and descriptions clearly delineate boundaries.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (run_privileged, request_path_access, fetch_url, check_request), but sandbox_status breaks the pattern by being noun_noun. The deviation is minor and the intent remains clear.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of gated external operations. Each tool earns its place without redundancy or excess.

    Completeness5/5

    The surface covers all core operations (run, file, fetch) and provides status retrieval via check_request and sandbox_status. No obvious dead ends or missing lifecycle steps for the stated escalation workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources