Skip to main content
Glama
Kisyntra

agent-sudo-mcp

by Kisyntra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-sudo-mcp

No user-submitted related servers found.

    Related Servers

    • Dvarapala

      demolished-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.
      MIT

    • enterprise-agent-lab

      isaac-dev-ai
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.
      1
      -

    • AgentGate

      agentkitai
      A
      license
      A
      quality
      A
      maintenance
      Human-in-the-loop approval gateway for agent tool calls: agents request, policies decide, humans approve via Slack/Discord/web — with an OWASP-LLM-Top-10-tagged audit trail. Self-hostable.
      10
      18 npm
      33
      MIT
    • agentguard by agentwares

      agentguardofficial

      agentwares
      A
      license
      Not graded
      quality
      C
      maintenance
      Enforces policy controls for AI agents, including spend limits, action approvals, kill switch, scoped credentials, dry-run diffs, loop prevention, and auditable hash-chained logs.
      MIT
    • Proofpane by Proofpane

      Proofpaneofficial

      Proofpane
      A
      license
      B
      quality
      A
      maintenance
      A governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.
      13
      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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: getting runtime context, reading files, running shell commands, and writing files. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern (get_runtime_context, read_file, run_shell_command, write_file), providing a consistent and predictable interface.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its demo/reference purpose. The count is not too low or too high for the functionality offered.

    Completeness4/5

    The tools cover the core operations (read, write, execute, context), but it lacks common file operations like listing or deletion, which may be needed for full workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources