aiganak-aiops-mcp
Related Servers
Alternatives to aiganak-aiops-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides telemetry tools for retrieving recent logs and system metrics to support root-cause analysis of infrastructure incidents. Enables autonomous incident triage with grounded verification and human-in-the-loop remediation.1-
- FlicenseNot gradedqualityDmaintenanceEnables autonomous infrastructure health management by exposing tools for retrieving system logs, querying a knowledge base, executing SQL analytics, and simulating system commands, all integrated into an AI-driven incident response workflow.-
- AlicenseNot gradedqualityDmaintenanceEnables AI clients to inspect backend systems through structured engineering tools including Git history, Winston logs, OpenAPI contracts, and sandboxed source code.2ISC
- AlicenseAqualityBmaintenanceEnables developers and AI agents to compress context, plan token budgets, rerank results, patch code, analyze ASTs and dependencies, isolate stack traces, compile polyglot types, solve deterministic math, schedule constraints, judge A/B tests, and diff agent memory checkpoints through 12 specialized tools.151MIT
- FlicenseAqualityCmaintenanceEnables natural-language diagnosis of Linux system issues by providing sandboxed, typed tools for system, service, filesystem, and git inspection, with human approval for mutating actions.18-
- FlicenseAqualityDmaintenanceEnables LLM-driven agents to autonomously detect, diagnose, repair, verify, and prevent software and hardware failures on local and remote systems. Includes built-in safety checks and automatic rollbacks.15-
TDQS
Scored across 3 tools
Each tool targets a clearly distinct task: log querying, code inspection, and code modification. There is no overlap between querying logs, parsing ASTs, and applying patches, so an agent would not confuse them.
The naming is inconsistent: query_log_file uses a verb_noun_obj pattern, inspect_code_ast uses verb_noun_obj, but apply_code_patch uses verb_noun. The verbs (query, inspect, apply) are varied and not obviously part of a unified domain vocabulary, and the patterns differ across tools.
Three tools is on the borderline of being too thin for an AIOps server, especially given the mixed domain of log analysis and code modification. The count is defensible, but the scope feels narrow for a server with 'aiops' in its name.
The tools span log querying, code inspection, and code patching, but each area has obvious gaps: there is no tool for writing log query results, no update/get verification for the patch step beyond the patch itself, and the log analysis surface gives no way to define or manage analysis workflows. The domain coverage is fragmented rather than complete.