Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kubernetes Troubleshoot

OCI · DOCKER.IO/YAWGYAMFIPREM32/K8S-TROUBLESHOOT-MCP:1.0.0 · SCANNED AUG 26

Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes.

Available components

oci · docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0 7
7 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency35
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the Kubernetes Troubleshoot MCP server?

Kubernetes Troubleshoot runs locally as a container image, launched with docker run --rm -i docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0

# add to Claude Code
claude mcp add nanagyamfiprempeh30-k8s-troubleshoot-mcp -- docker run --rm -i docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0
// .cursor/mcp.json
{
  "mcpServers": {
    "nanagyamfiprempeh30-k8s-troubleshoot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nanagyamfiprempeh30-k8s-troubleshoot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add nanagyamfiprempeh30-k8s-troubleshoot-mcp -- docker run --rm -i docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nanagyamfiprempeh30-k8s-troubleshoot-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  nanagyamfiprempeh30-k8s-troubleshoot-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nanagyamfiprempeh30-k8s-troubleshoot-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "nanagyamfiprempeh30-k8s-troubleshoot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 7

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 26 Aug 2026 · Analysed oci/docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason Verification failed
Discovered via OCI referrers API
MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Kubernetes Troubleshoot MCP server?

Kubernetes Troubleshoot is an MCP server listed in the public MCP registry as io.github.NanaGyamfiPrempeh30/k8s-troubleshoot-mcp. Read-only Kubernetes diagnostics: pods, logs, events, workloads, services, PVCs and nodes. This page covers its container image (docker.io/yawgyamfiprem32/k8s-troubleshoot-mcp:1.0.0).

Is the Kubernetes Troubleshoot MCP server safe to use?

Kubernetes Troubleshoot scores 7 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Kubernetes Troubleshoot MCP server still maintained?

Kubernetes Troubleshoot is still listed as active in the MCP registry. We last reached this channel on 26 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Kubernetes Troubleshoot MCP server under?

Kubernetes Troubleshoot declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.