Praxis
Related Servers
Alternatives to Praxis
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables users to investigate infrastructure incidents in plain English, correlate observability and deploy data with runbooks, and get evidence-backed root-cause proposals with approval-gated remediation.5-
- FlicenseNot gradedqualityDmaintenanceAn MCP-native AI incident response system that empowers agents to investigate production incidents, collect evidence, hypothesize root causes, and drive controlled remediation and recovery verification.1-
- AlicenseAqualityBmaintenanceEnables AI agents to safely inspect and execute version-controlled operational runbooks with policy checks, dry-run planning, and out-of-band approvals.3MIT
- 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
- AlicenseBqualityAmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables cloud and platform engineers to investigate AWS incidents by grounding responses in approved runbooks and operational evidence, with authenticated access, citations, observability, and human approval before any write action.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: initiating remediation, retrieving run records, fetching artifact diffs, approving/rejecting, and checking integration status. No overlap in functionality.
All tool names follow the consistent pattern 'praxis_verb_noun' using snake_case, e.g., praxis_prepare_remediation, praxis_get_run. No deviations.
Five tools is well-scoped for a remediation workflow server covering initiation, status retrieval, artifact access, approval, and integration checks. Each tool earns its place.
Covers the core workflow end-to-end (prepare, retrieve, approve, check status). Minor gap: no listing or searching runs; agents must know the run ID, but this is acceptable for the focused domain.