K8s Lens
PYPI · K8S-LENS-MCP
MCP server for natural-language Kubernetes operations across single or multi-cluster environments.
Available components
Last scanned (11 hours ago)
Scores higher than 58% of PyPI servers
Category Cloud Infrastructure
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 Security45
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known medium-severity CVE affects opentelemetry-api 1.29.0, reached via opentelemetry-instrumentation > opentelemetry-semantic-conventions > opentelemetry-api. A fixed version is available. View diagnostics → Fail
- Runs poetry.core.masonry.api at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 60 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 169 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 812 tokens (~116/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.77 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.93 functional
- 23 Oct 26 −1
- CVE-2026-114603 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.80 → pass security
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 5 Nov 2026 · Analysed pypi/k8s-lens-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | poetry.core.masonry.api |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-xcq7-p3pf-p88h | CVE-2026-114603 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 60 packages
| Packages resolved | 60 |
|---|---|
| Stale | 1 |
| 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 →
advise_resources ~79
Scan the cluster for resource optimization opportunities. Identifies idle pods, over-provisioned CPU/memory, missing HPAs, and orphaned PVCs. Example prompts: 'Find waste in the cluster', 'Which pods are over-provisioned?', 'Show me idle resources'.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | – | – | Namespace to scope to. Omit for all namespaces. |
No output schema declared.
No examples provided.
analyze_pod ~124
Perform deep root-cause analysis on a failing or misbehaving pod. Correlates pod status, recent events, container logs, resource limits, and node conditions to diagnose the issue. Example prompts: 'Why is my-pod failing?', 'Why does my-pod keep restarting?', 'Diagnose pod my-pod in namespace production'.
| Name | Type | Req | Description |
|---|---|---|---|
| container | – | – | Specific container for multi-container pods |
| namespace | – | – | Pod namespace |
| pod_name | string | yes | Name of the pod to analyze |
| tail_lines | integer | – | Number of log lines to fetch |
No output schema declared.
No examples provided.
compare_deployments ~144
Diff two Kubernetes resources (e.g., Deployments) across namespaces or clusters. Strips volatile metadata (UIDs, resourceVersions, timestamps) and returns a structured diff showing added, removed, and changed fields. Example prompts: 'Diff the nginx deployment between staging and prod', 'Compare the api deployment in dev vs production'.
| Name | Type | Req | Description |
|---|---|---|---|
| context_a | – | – | Context for first resource |
| context_b | – | – | Context for second resource |
| name | string | yes | Name of the resource |
| namespace_a | string | yes | Namespace of first resource |
| namespace_b | string | yes | Namespace of second resource |
| resource_kind | string | – | Kind of resource to diff |
No output schema declared.
No examples provided.
compare_helm_releases ~113
Diff Helm releases across namespaces or clusters. Compares rendered manifests and values to detect drift. Example prompts: 'Diff the nginx Helm release between staging and prod', 'Compare the api release values in dev vs production'.
| Name | Type | Req | Description |
|---|---|---|---|
| context_a | – | – | Context for first release |
| context_b | – | – | Context for second release |
| namespace_a | string | yes | Namespace of first release |
| namespace_b | string | yes | Namespace of second release |
| release_name | string | yes | Name of the Helm release to compare |
No output schema declared.
No examples provided.
generate_manifest ~129
Generate best-practice Kubernetes YAML manifests from a natural language description. Supports Deployments, Services, Ingresses, and ConfigMaps. Returns valid, ready-to-apply YAML with sensible defaults for replicas, resource requests, probes, and labels. Example prompts: 'Create a basic nginx deployment with 2 replicas and a LoadBalancer service', 'Generate a Redis deployment with a ClusterIP service on port 6379'.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Natural language description of desired resources |
| kind | – | – | Specific kind: Deployment, Service, Ingress, ConfigMap |
| namespace | – | – | Target namespace |
No output schema declared.
No examples provided.
get_resources ~193
Query Kubernetes resources with flexible filters. Supports pods, deployments, services, nodes, and more. Filter by namespace, status, labels, or field selectors. Example prompts: 'Show me all pods with status CrashLoopBackOff in namespace staging', 'List all deployments in the default namespace', 'Get nodes with label zone=us-east-1'.
| Name | Type | Req | Description |
|---|---|---|---|
| contexts | array | – | Kubernetes contexts to query. If empty, uses the default context. |
| field_selector | – | – | Raw field selector string |
| labels | – | – | Label selector as key-value pairs |
| limit | integer | – | Maximum results to return |
| namespace | – | – | Namespace to query. Omit for all namespaces. |
| resource_type | string | yes | Resource type, e.g. 'pods', 'deployments', 'services', 'nodes' |
| status | – | – | Filter by status phase, e.g. 'Running', 'Pending', 'CrashLoopBackOff' |
No output schema declared.
No examples provided.
health ~30
Check the server health and connectivity to the Kubernetes cluster. Returns the server status, configured context, and default namespace.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the K8s Lens MCP server?
K8s Lens runs locally as a PyPI package, launched with uvx k8s-lens-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · k8s-lens-mcp
claude mcp add firas-mcp-servers-k8s-lens-mcp -- uvx k8s-lens-mcp
What is the K8s Lens MCP server?
K8s Lens is an MCP server listed in the public MCP registry as io.github.firas-mcp-servers/k8s-lens-mcp. MCP server for natural-language Kubernetes operations across single or multi-cluster environments. This page covers its PyPI package (k8s-lens-mcp).
Is the K8s Lens MCP server safe to use?
K8s Lens scores 60 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. 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 K8s Lens MCP server expose?
K8s Lens exposes 7 tools: health, get_resources, analyze_pod, compare_deployments, generate_manifest, and 2 more. Their descriptions and schemas cost roughly 812 tokens of context every time the server is loaded.
Is the K8s Lens MCP server still maintained?
K8s Lens is still listed as active in the MCP registry. We last reached this channel on 5 November 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 K8s Lens MCP server under?
K8s Lens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.