Kubernetes Troubleshoot
Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes.
The current version, v1.0.0, was published to the official MCP registry on 2026-08-24. It is distributed as the Docker image docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0, filed under Kubernetes by this index, and declares 5 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using Kubernetes Troubleshoot in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No malicious instructions”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-10-30).
Contracts can change after screening, with no version bump. The gate pins Kubernetes Troubleshoot’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for Kubernetes Troubleshoot](https://mcpindex.ai/server/io-github-nanagyamfiprempeh30-k8s-troubleshoot-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-nanagyamfiprempeh30-k8s-troubleshoot-mcp">Independent trust record for Kubernetes Troubleshoot</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-nanagyamfiprempeh30-k8s-troubleshoot-mcp)<a href="https://mcpindex.ai/server/io-github-nanagyamfiprempeh30-k8s-troubleshoot-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-nanagyamfiprempeh30-k8s-troubleshoot-mcp" alt="mcpindex verdict" height="20" /></a>KUBECONFIGPath to the kubeconfig inside the container. Must match the mount destination. There is no fallback to ~/.kube/config and no in-cluster config: a missing, unreadable or malformed file is a startup failure rather than a silent downgrade to an ambient credential.
ALLOWED_NAMESPACESComma-separated namespaces the server may read, e.g. staging,production. Wildcards (* and all) are rejected at startup, and kube-system and kube-public are stripped even if listed. This is defense-in-depth, not the security boundary — the boundary is the ServiceAccount's RBAC bindings.
LOG_LEVELDEBUG, INFO, WARNING or ERROR. All logging goes to stderr; stdout carries the JSON-RPC stream exclusively.
API_TIMEOUT_SECONDSKubernetes API request timeout. Must be a positive integer.
MAX_LOG_LINESMaximum log lines any single get_pod_logs call may return. Must be a positive integer; clamped to a hard ceiling of 1000 with a warning.
List Civo instances, Kubernetes clusters, networks and DNS; reboot instances, add rules.
Governed Docker and Kubernetes operations for AI agents: scoped keys, guardrails, human approvals.
Unified MCP server for Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki