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 npm2Apache 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.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceA human-in-the-loop SSH bridge for AI agents that requires approval for every command before execution on configured servers.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to use individual allowlisted 1Password items by running pre-approved commands one at a time, with each call requiring explicit user approval. Secrets are injected only into the child process environment and masked from the agent, which receives just exit code and output.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct action and resource: execute runs approved commands, start_server/stop_server manage daemons, status reports state, and update_host edits registry metadata. No overlapping purposes or ambiguous boundaries.
Three tools follow a clear verb_noun snake_case pattern (start_server, stop_server, update_host), but execute is a bare verb and status is a bare noun. The deviations are minor and still readable, so mostly consistent.
Five tools is well-scoped for a proxy/daemon manager; each tool covers a necessary lifecycle operation (start, execute, status, stop, update host metadata) without redundancy.
The surface covers daemon lifecycle (start, execute, status, stop) and host metadata update, but lacks a way to remove or delete a host from the registry. Status partially covers listing, so the gap is minor.