io.github.mikhae1/kubeview
NPM · KUBEVIEW-MCP · SCANNED SEP 20
Read-only Model Context Protocol MCP server enabling code-driven AI analysis of Kubernetes clusters.
Available components
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 119 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 370 tokens (~123/item across 3 items; 2 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_code" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.mikhae1/kubeview MCP server?
io.github.mikhae1/kubeview runs locally as an npm package, launched with npx -y kubeview-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · kubeview-mcp
claude mcp add mikhae1-kubeview -- npx -y kubeview-mcp
{
"mcpServers": {
"mikhae1-kubeview": {
"command": "npx",
"args": [
"-y",
"kubeview-mcp"
]
}
}
} {
"servers": {
"mikhae1-kubeview": {
"command": "npx",
"args": [
"-y",
"kubeview-mcp"
]
}
}
} codex mcp add mikhae1-kubeview -- npx -y kubeview-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mikhae1-kubeview": {
"type": "local",
"command": [
"npx",
"-y",
"kubeview-mcp"
],
"enabled": true
}
}
} openclaw mcp add mikhae1-kubeview --command npx --arg -y --arg kubeview-mcp
mcp_servers:
mikhae1-kubeview:
command: "npx"
args: ["-y", "kubeview-mcp"] {
"McpServers": {
"mikhae1-kubeview": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"kubeview-mcp"
]
}
}
} assistant mcp add mikhae1-kubeview -t stdio -c npx -a -y kubeview-mcp
{
"mcpServers": {
"mikhae1-kubeview": {
"command": "npx",
"args": [
"-y",
"kubeview-mcp"
]
}
}
} 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.
- 20 Sept 26 −2
- Stability: pass → 0.83 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.77 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/kubeview-mcp@2.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 119 packages
| Packages resolved | 119 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
kube_pod_exec Execute Command in Kubernetes Pod ~256
Execute a command in a container of a pod via the Kubernetes API (no kubectl). Captures stdout/stderr and returns them when the command completes.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Exact argv to execute without a shell, e.g., ["/bin/ls","-la"]. Provide this OR command. |
| argv | string | – | Whitespace-separated argv to execute without a shell (e.g., "/usr/bin/env printenv"). Convenience for CLI; prefer args[] when possible. |
| command | string | – | Shell command to run. Defaults to trying /bin/bash first, then /bin/sh, then other common shells. Provide this OR args[]. |
| container | string | – | Container name (optional; defaults to first container) |
| namespace | string | – | Kubernetes namespace (defaults to "default") |
| podName | string | yes | Name of the target Pod |
| shell | string | – | Shell binary used when command is provided (default /bin/sh) |
| stdin | string | – | Optional data to write to process stdin before closing it |
| timeoutSeconds | number | – | Maximum time to wait for command completion (default 60s) |
| tty | boolean | – | Allocate a TTY (default false) |
| Name | Type | Req | Description |
|---|---|---|---|
| command | array|string | – | – |
| status | – | – | – |
| stderr | string | yes | – |
| stdout | string | yes | – |
No examples provided.
run_code Run Kubernetes Analysis Code ~108
Execute bounded TypeScript with top-level await against progressively discovered Kubernetes capabilities. Use tools.list(), tools.search(), tools.help(), and typed namespaces; inspect tools.disabled() for policy denials. Return a value from the script. Full documentation and types are available through the code-mode prompt and file:///sys/global.d.ts.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | TypeScript code to execute via the sandboxed runtime. Top-level await is supported. |
| input | string | – | Optional input payload available to the script. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| isError | boolean | – | – |
| result | – | – | – |
| stderr | string | – | – |
| stdout | string | – | – |
| success | boolean | yes | – |
No examples provided.
What is the io.github.mikhae1/kubeview MCP server?
io.github.mikhae1/kubeview is an MCP server listed in the public MCP registry as io.github.mikhae1/kubeview. Read-only Model Context Protocol MCP server enabling code-driven AI analysis of Kubernetes clusters. This page covers its npm package (kubeview-mcp).
Is the io.github.mikhae1/kubeview MCP server safe to use?
io.github.mikhae1/kubeview scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.
What tools does the io.github.mikhae1/kubeview MCP server expose?
io.github.mikhae1/kubeview exposes 2 tools: run_code, kube_pod_exec. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.
Is the io.github.mikhae1/kubeview MCP server still maintained?
io.github.mikhae1/kubeview is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.mikhae1/kubeview MCP server under?
io.github.mikhae1/kubeview declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.