opsgate
Related Servers
Alternatives to opsgate
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLocal zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.465 PyPI5Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.1211 npm1MIT
- AlicenseBqualityCmaintenanceEnables AI tools to perform server operations such as log inspection, system monitoring, code management, Nginx and certificate management, with support for local and remote SSH modes and built-in security controls.2353 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local proxy in front of any MCP server for developers on Claude Code or Cursor: see every tool call your agent makes, hold the risky ones for your approval, and keep a secret-redacted journal that is tamper-evident with an external anchor.752 npm1Apache 2.0
- AlicenseAqualityCmaintenanceHuman-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.1018 npm33MIT
- AlicenseAqualityAmaintenanceLeast-privilege compiler and MCP gateway for AI agents: run your agent in record-only mode, compile the smallest policy it actually needs from its real tool calls, enforce it at the gateway (deny > approve > allow), and keep a SHA-256 hash-chained audit of every call that verifies offline.1493 npm1Apache 2.0
TDQS
Scored across 25 tools
Each tool targets a distinct resource and action, with clean separation between Docker, systemd, nginx, file, and diagnostic operations. The only nominal overlap is journal_errors vs journal_tail, but the descriptions clearly differentiate a broad error triage from a filtered tail.
All tools use consistent snake_case with a resource prefix (docker_, service_, file_, nginx_, journal_), making the surface predictable. Minor inconsistency exists because some suffixes are nouns (docker_ps, docker_stats) while others are verbs (docker_start, service_restart), but the grouping remains readable.
At 25 tools, the set sits at the upper end of the 16-25 range, which the rubric treats as heavy. The breadth across five ops subdomains justifies many, but some lifecycle tools (start/stop/restart/reload) could be consolidated, making the count borderline rather than lean.
Coverage is strong for diagnostics and basic lifecycle control across Docker, systemd, nginx, and files, with no obvious dead ends for triage. Minor gaps include no service enable/disable, no Docker remove/exec, and no file write/delete, which may be intentional for a read/control-focused ops tool.