mcp · handle k8s_aiops
k8s_mcp_server_2 · job 86%MCP K8s Observability · job 83%kube-sentinel-mcp · job 82%Kubescout MCP · job 81%thinkneo_ai_control_plane · job 71%Kube Triage · job 74%clusterport · job 82%Proofpane · job 72%mcp_server_kubernetes · job 88%Janus MCP · job 77%kubemetes_introducing_headlamp · job 80%MCP K8S Go · job 82%kube-mcp · job 84%radar_mcp · job 88%mcp_kubernetes_ro · job 73%Kube Observer MCP · job 82%k8s_mcp_server · job 80%kube-handrail · job 79%k8s_pilot · job 76%MCP-AgentGym · job 75%mcp_kubernetes_server · job 78%Container-Host-AIops · job 76%infrastructure_mcp · job 77%k8s-troubleshoot-mcp · job 80%Kube Check MCP · job 76%阿里云容器服务 MCP Server (ack-mcp-server) · job 79%kubernetes_mcp_server · job 85%kubelint-mcp · job 75%mcp-k8s-eye · job 92%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series