ops-mcp
Related Servers
Alternatives to ops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables autonomous digital forensics and incident response by wrapping SIFT Workstation tools as MCP tools and orchestrating a multi-agent AI pipeline for evidence analysis and remediation planning.2MIT
- AlicenseNot gradedqualityAmaintenanceProvides MCP tools that give AI agents persistent, append-only memory in a git repository, letting them record observations, decisions, and corrections while retrieving context briefs, current facts, conflicts, and traceable event history without a vector database.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to analyze repository architecture, changed-file and diff impact, dependency and endpoint exposure, API contract compatibility, architecture boundaries, bounded capacity simulations, and security/quality evidence through MCP tools.3Apache 2.0
- FlicenseAqualityCmaintenanceEnables AI agents to perform digital forensics and incident response tasks by dynamically discovering and utilizing host tools for memory analysis, metadata extraction, threat detection, and file dissection.51-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect Autopsy forensic cases through read-only MCP tools for case metadata, filesystem and artifact search, timeline and account queries, evidence extraction, and hash-chained audit/seal verification.10 npm2GPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables an AI agent to audit an untrusted repository through eight parameterless MCP tools that run ten pinned security scanners inside a hardened container, returning native scanner reports, a run manifest tied to the scanned tree, and an audit log. The agent gets no shell, no target path, and no way to build or execute the audited code, so hostile repositories cannot steer the analysis.Apache 2.0
TDQS
Scored across 3 tools
container_autopsy and container_obituary substantially overlap—both diagnose why a container died, examine logs, and output a markdown report. An agent would struggle to reliably choose between them despite the slight difference in depth and tone. git_sins is the only clearly distinct tool.
All three tools follow a consistent lowercase_snake_case pattern with a domain prefix and a thematic noun: container_autopsy, container_obituary, git_sins. The pattern is predictable and readable, though the playful nouns deviate slightly from conventional verb_noun naming.
Three tools is on the thin side for a server named 'ops-mcp', but the set is tightly focused on diagnostics and forensics. It feels more like a themed utility collection than an operational coverage layer, which is acceptable but not rich.
The scope is narrow—container death investigation and git history analysis—and within that scope the tools cover their stated purposes. However, the two container tools are redundant rather than complementary, and there is no action-oriented tooling (e.g., restart, cleanup) that an 'ops' user might expect.