Skip to main content
Glama
Santi746

hitl-proxy

by Santi746
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to hitl-proxy

No user-submitted related servers found.

    Related Servers

    • MCP ToolHub

      zhihaochen67
      F
      license
      A
      quality
      A
      maintenance
      Enables coding agents to perform workspace-confined file operations, read-only Git inspection, and structured shell commands, while requiring out-of-band human approval for mutations and external executions and maintaining an audit trail.
      14
      3
      -

    • Agent File Guardian

      ShinYeol-Lee
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a human-in-the-loop security layer for AI agents by intercepting file operations, explaining them with a local LLM, and enforcing a deterministic policy that requires user approval for risky actions.
      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.
      88 npm
      1
      -

    • AgentGuard MCP Server

      vaasu202
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.
      -

    • Kaiza MCP Server

      dylanmarriner
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables secure, audited file operations with LLMs by enforcing implementation plans, restricting writes to approved file scopes, and maintaining a tamper-evident audit log with stub detection.
      291 npm
      -
    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

    Disambiguation4/5

    Each tool targets a distinct action (declare intent, edit, write, bash), but edit_hitl and write_hitl both handle file changes and the relationship between declare_intent_hitl's sessionToken and the per-action sessionToken is not fully clear. Overall, agents should be able to select the right tool with the guidance provided.

    Naming Consistency4/5

    All tools share the _hitl suffix and follow a verb prefix pattern. declare_intent_hitl uses a compound verb while the others use single verbs, creating a slight inconsistency, but the pattern remains predictable and readable.

    Tool Count5/5

    Four tools is well-scoped for a proxy server that adds human-in-the-loop approval to common operations. Each tool has a clear role and no redundant entries inflate the surface.

    Completeness4/5

    The server covers the core file edit/write and shell execution actions needed for an approval proxy, plus an explicit intent declaration step. Missing session audit/cancel tools are minor gaps that don't block the primary workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources