MCP server that diagnoses unhealthy Kubernetes workloads and finds resource right-sizing candidates using real cluster state - not another kubectl wrapper.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"triagekit-mcp-k8s-triage","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# triagekit-mcp-k8s-triage Part of the [TriageKit](https://github.com/Karthick-dev-cart/triagekit-mcp) MCP server suite. Diagnoses unhealthy Kubernetes workloads and finds resource right-sizing candidates using real cluster state — not another `kubectl` wrapper. Existing Kubernetes MCP servers mostly expose cluster CRUD; this one narrows hard on read-only diagnosis and right-sizing. ## Why When a pod is crash-looping, an on-call engineer pivots across `kubectl describe`, `kubectl logs`, rollout history, and (if they're lucky) a Grafana dashboard to figure out what's actually wrong. This server does that correlation directly: container exit codes and event reasons get mapped to a ranked failure category, crashes get checked against recent rollouts, and Prometheus usage history gets compared against resource requests — all as structured evidence, not another raw JSON dump. ## Tools | Tool | What it does | |---|---| | `diagnose_workload` | Classifies a pod/deployment's failure as OOMKilled, image-pull error, config error, probe failure, or scheduling failure, with evidence | | `explain_pod_events` | Orders a pod's raw Kubernetes events into a time-sequenced narrative | | `get_pod_logs_since_last_restart` | Fetches logs from the container's current run only, so an old crash's logs don't drown out the current state | | `correlate_crashloop_with_recent_changes` | Checks whether a crash lines up with a recent rollout (deploy-related vs. pre-existing bug) | | `find_resource_right_sizing_candidates` | Compares Prometheus usage history against resource requests, flags over/under-provisioned workloads | | `cluster_health_summary` | One-shot digest: node pressure, failed/pending pods, PDB violations, HPAs at max | Also exposes a resource (`k8s://{context}/{namespace}/{workload}/diagnosis`) and a prompt (`incident_response_runbook`) that walks an LLM through the standard triage sequence. This server is **read-only** by design — see [SECURITY.md](SECURITY.md). It never c…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.