A
licenseNot graded
qualityC
maintenanceMCP server that diagnoses ML model regressions by correlating drift reports, eval runs, and deploy logs, providing evidence-cited incident reports through a set of investigation tools.
1
MIT
mendrift-mcp
by suneel190700
Related Servers
Alternatives to mendrift-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA multi-agent MCP server that turns LLMs into an autonomous incident-response copilot, enabling rapid investigation, correlation, and remediation of production incidents.MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables autonomous self-healing AIOps by monitoring system metrics and executing dynamic remediation through LLM-driven tool routing, with support for Streamlit UI and CLI.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that diagnoses GitHub Actions workflow failures and automatically creates repair pull requests using LLM-generated unified diffs. It includes a governance layer to orchestrate autonomous fixes or human-reviewed repairs based on risk assessment thresholds.-
- AlicenseBqualityDmaintenanceMCP server for AI-assisted trading operations, enabling agents to diagnose and resolve FIX, OMS, and venue incidents through controlled tools and human approval.38MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that coordinates autonomous infrastructure health monitoring agents, enabling natural-language telemetry queries and automated diagnosis, remediation, and verification.-
TDQS
A3.9/5.0
Scored across 7 tools
Disambiguation5/5
Each tool targets a distinct action and resource: drift reports, metric anomalies, deployment history, deployment diffs, incidents, and rollback planning/execution. There is no ambiguity between tools like propose_rollback and execute_rollback because one is read-only planning and the other is execution.
Naming Consistency5/5
All tools use lowercase snake_case with a verb_noun pattern (propose_rollback, execute_rollback, open_incident, get_drift_report, summarize_metric_anomalies, get_deployment_history, diff_deployments). The naming is uniform and predictable, making it easy to infer tool behavior from the name.
Tool Count5/5
Seven tools is a well-scoped count for a drift monitoring and mitigation server. Each tool covers a distinct part of the workflow—detection, investigation, incident management, and rollback—without unnecessary redundancy or overwhelming the agent.
Completeness4/5
The core lifecycle is covered: drift detection, anomaly summarization, deployment history/diffing, incident opening, and rollback proposal/execution. The main gap is that incidents can be opened but not listed, closed, or updated, and there is no rollback status tracking. These are workable gaps but slightly incomplete for a full incident management loop.
Maintenance
ActivitySlowing
ResponsivenessNo issues