ops-graph
Related Servers
Alternatives to ops-graph
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to trace upstream dependencies and downstream blast radius across a Neo4j-modeled service topology, rank root-cause hypotheses, and score composite risk from graph, temporal, git-diff, and trace signals. It also stages rollback-ready remediation plans that execute only after human approval and the required scope.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceLets AI agents query a computerized system inventory as a knowledge graph using Cypher, enabling blast radius, data lineage, regulation checks, and change impact assessments while preventing hallucinated regulatory claims.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to traverse a FalkorDB service graph by reading topology and open incidents, running graph algorithms, and executing multi-hop root-cause investigations whose LOCATE, SUGGEST and PROPOSE stages persist as resumable traces. It also surfaces episodic memories and searches runbooks and ownership records, while keeping raw Cypher, tenant switching, approvals and simulation out of reach.MIT
- AlicenseBqualityBmaintenanceEnables coding agents to diagnose production incidents by traversing a FalkorDB graph of services, deploys, feature flags, owners and past incidents to find the true root cause rather than the alerting service. It also lets agents act on that reasoning — rolling back, restarting or flipping flags with dry-run-first safety — then verify recovery, notify owners, and store the incident and its fix as memory for faster future resolution.241Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to safely inspect and execute version-controlled operational runbooks with policy checks, dry-run planning, and out-of-band approvals.3MIT
- FlicenseNot gradedqualityDmaintenanceTransforms code repositories and development documentation into a queryable Neo4j knowledge graph, enabling AI assistants to perform intelligent code analysis, dependency mapping, impact assessment, and automated documentation generation across 15+ programming languages.7-
TDQS
Scored across 9 tools
Most tools map to distinct analytical questions: impact_analysis, root_cause_candidates, decommission_candidates, compliance_findings, and reconciliation_report each target a different report type. The main overlap is directionality between impact_analysis (downstream) and root_cause_candidates (upstream), but their descriptions explicitly clarify the direction. read_only_cypher is a deliberate catch-all escape hatch rather than a duplicate.
There is a mix of conventions: verb_noun tools (find_asset, describe_schema, search_docs), noun_phrase report tools (impact_analysis, compliance_findings, reconciliation_report), and a bare descriptor (read_only_cypher). Each name is readable and self-explanatory, but no single predictable pattern governs the set.
Nine tools is well within the sweet spot and each tool earns its place, covering a distinct analysis or lookup capability. No redundant or filler tools are present.
The read-only ops-graph surface covers dependency impact, root cause, decommission, compliance, data-quality reconciliation, schema introspection, doc search, asset lookup, and a query escape hatch — a solid lifecycle for read-only analysis. Minor gaps like a dedicated full-asset-detail/property listing exist, but find_asset plus read_only_cypher let agents work around them.