Skip to main content
Glama
JerryFish123

hitl-gate-mcp

by JerryFish123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to hitl-gate-mcp

No user-submitted related servers found.

    Related Servers

    • sandbox

      Boredem125
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to safely execute privileged commands by routing them to a human approver, who runs them outside the agent's context and returns the output to the model.
      5
      MIT

    • vantagate-mcp-server

      Aderix
      A
      license
      Not graded
      quality
      D
      maintenance
      Human-in-the-Loop authorization gateway for AI Agents. Securely pause MCP workflows and route high-risk actions to human approvers via Slack or Email.
      40 npm
      1
      MIT

    • Laguarde

      FuturPanda
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to evaluate actions against team-defined policies, record decisions, and obtain human approvals for potentially risky operations.
      58 npm
      1
      -
    • @quirna/mcp by quirna

      @quirna/mcpofficial

      quirna
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to request human approval before consequential actions, with policy-based routing, phone-based approver decisions, and signed audit evidence.
      MIT
    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 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: assess_and_gate is the main gating action, get_approval_status checks a specific ticket, list_approval_history provides audit history, list_dangerous_ops catalogs risky operations, list_pending shows pending tickets, and request_approval allows manual bypass. No two tools have ambiguous overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., list_pending, request_approval). The slight deviation in 'assess_and_gate' is minor and still clear.

    Tool Count5/5

    With 6 tools, the server covers the essential operations for human-in-the-loop gating without being excessive or sparse. Each tool handles a specific, necessary function.

    Completeness5/5

    The tool set covers the full lifecycle: assessment (assess_and_gate), manual request (request_approval), status checking (get_approval_status), pending list (list_pending), history (list_approval_history), and catalog (list_dangerous_ops). No obvious gaps for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources