sudo-proxy
OfficialRelated Servers
Alternatives to sudo-proxy
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables secure execution of shell commands through a dynamic approval system that prompts for user authorization on first use, with persistent command storage and comprehensive audit logging.Apache 2.0
- AlicenseAqualityBmaintenanceEnables 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.5MIT
- AlicenseNot gradedqualityBmaintenanceProvides local command execution, remote SSH, interactive terminals, file read/write, and source search for AI CLI through stdio, with large output pagination and safety confirmations.6 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables controlled delegation of tasks to local coding-agent CLIs and the Manus API, with strict sandboxing, approval tracking, and remote-egress safeguards.12 npmMIT
- AlicenseNot gradedqualityDmaintenanceA human-in-the-loop SSH bridge for AI agents that requires approval for every command before execution on configured servers.MIT
- AlicenseAqualityBmaintenanceEnables executing local commands via an argv-based tool with optional non-interactive sudo, command allowlisting, and filesystem write confinement using Bubblewrap.2MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: execute runs commands, start/stop manage the daemon lifecycle, status queries state, and update_host edits registry metadata. There is no ambiguity between tools, and descriptions reinforce their unique roles.
Most tool names follow a verb_noun pattern (update_host, start_server, stop_server), while 'execute' and 'status' are verbs/nouns without an explicit direct object. This is a minor deviation but still predictable and readable, so it warrants a slight deduction.
With only 5 tools, the server is tightly scoped to its purpose: daemon lifecycle (start, stop, status), command execution, and host metadata management. Each tool earns its place, and the count is ideal for a focused utility server.
The tool set covers the core lifecycle (start, stop, status) plus the main action (execute) and host registry updates. A missing feature like removing a host is a minor gap that agents can work around, and the surface is otherwise complete for the domain.