io.github.sophotechlabs/kube-lint-mcp
OCI · GHCR.IO/SOPHOTECHLABS/KUBE-LINT-MCP:0.8.9 · 2 COMPONENTS
Validate Kubernetes manifests, Helm charts, Kustomize overlays, and FluxCD resources
Available components
Last scanned (7 hours ago)
Scores higher than 71% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Build provenance not yet verified. View diagnostics → Unverified
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 960 tokens (~80/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −4
- Stability: pass → 0.77 functional
- 13 Oct 26 +1
- Stability: 0.97 → 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 oci/ghcr.io/sophotechlabs/kube-lint-mcp:0.8.9
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | oci |
| Reason | Unsupported forge |
| Discovered via | OCI referrers API |
Background: How many MCP packages publish verified provenance →
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 →
argocd_app_diff ~129
Show diff between live and desired state of an ArgoCD application. Returns unified diff output showing what would change on sync. Exit 0 = in sync, exit 1 = has diff, exit 2 = error. Uses --core mode (kubeconfig only, no ArgoCD server auth needed). Requires select_kube_context to be called first.
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Name of the ArgoCD Application (required) |
| namespace | string | – | Namespace where the Application CR lives (optional). Common values: 'argocd', 'argo-cd' |
No output schema declared.
No examples provided.
argocd_app_get ~107
Get detailed status of a single ArgoCD application including sync/health status, conditions, and resource statuses. Uses --core mode (kubeconfig only, no ArgoCD server auth needed). Requires select_kube_context to be called first.
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Name of the ArgoCD Application (required) |
| namespace | string | – | Namespace where the Application CR lives (optional). Common values: 'argocd', 'argo-cd' |
No output schema declared.
No examples provided.
argocd_app_list ~82
List all ArgoCD applications with sync and health status. Uses --core mode (kubeconfig only, no ArgoCD server auth needed). Requires select_kube_context to be called first.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | Namespace where ArgoCD Application CRs live (optional). Common values: 'argocd', 'argo-cd' |
No output schema declared.
No examples provided.
flux_check ~31
Run 'flux check' to verify Flux installation and components health. Requires select_kube_context to be called first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flux_dryrun ~68
Validate FluxCD manifests with kubectl dry-run (client + server). ALWAYS use this before committing Flux YAML files to prevent GitOps reconciliation failures. Requires select_kube_context to be called first.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to YAML file or directory containing manifests (required) |
No output schema declared.
No examples provided.
flux_status ~28
Get Flux reconciliation status for all resources across namespaces. Requires select_kube_context to be called first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
helm_dryrun ~111
Validate Helm chart by rendering and running kubectl dry-run (client + server). ALWAYS use this before committing Helm chart changes to prevent deployment failures. Requires select_kube_context to be called first.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_path | string | yes | Path to Helm chart directory (required) |
| namespace | string | – | Namespace for rendering (optional) |
| release_name | string | – | Release name for helm template (default: 'release-name') |
| values_file | string | – | Path to values file (optional) |
No output schema declared.
No examples provided.
kubeconform_validate ~114
Validate Kubernetes manifests against JSON schemas offline using kubeconform. Catches invalid fields, type mismatches, and missing required fields without a live cluster. Does NOT require select_kube_context.
| Name | Type | Req | Description |
|---|---|---|---|
| kubernetes_version | string | – | Kubernetes version for schema lookup (e.g. '1.29.0'). Default: 'master' |
| path | string | yes | Path to YAML file or directory containing manifests (required) |
| strict | boolean | – | Reject additional properties not in the schema (default: false) |
No output schema declared.
No examples provided.
kustomize_dryrun ~82
Validate Kustomize overlay by building and running kubectl dry-run (client + server). ALWAYS use this before committing Kustomize overlay changes to prevent deployment failures. Requires select_kube_context to be called first.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to directory containing kustomization.yaml or path to kustomization.yaml file (required) |
No output schema declared.
No examples provided.
list_kube_contexts ~60
List available kubectl contexts. Use this to see available contexts, then ALWAYS present the list to the user and ask them which context they want to use before calling select_kube_context. NEVER automatically select a context without user confirmation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
select_kube_context ~79
Select the Kubernetes context for all subsequent operations. MUST be called before using any other tool. Does NOT mutate global kubeconfig — context is held in memory only. IMPORTANT: Do NOT call this automatically. Always list contexts first and ask the user which context to use.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Name of the kubectl context to use |
No output schema declared.
No examples provided.
yaml_validate ~69
Validate YAML syntax of Kubernetes manifest files. Catches syntax errors, duplicate keys, and tab indentation. Use this as a first-pass check before kubeconform or dry-run. Does NOT require select_kube_context.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to YAML file or directory containing YAML files (required) |
No output schema declared.
No examples provided.
How do I install the io.github.sophotechlabs/kube-lint-mcp server?
io.github.sophotechlabs/kube-lint-mcp runs locally as a container image, launched with docker run --rm -i ghcr.io/sophotechlabs/kube-lint-mcp:0.8.9. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/sophotechlabs/kube-lint-mcp:0.8.9
claude mcp add sophotechlabs-kube-lint-mcp -- docker run --rm -i ghcr.io/sophotechlabs/kube-lint-mcp:0.8.9
What is the io.github.sophotechlabs/kube-lint-mcp server?
io.github.sophotechlabs/kube-lint-mcp is listed in the public MCP registry as io.github.sophotechlabs/kube-lint-mcp. Validate Kubernetes manifests, Helm charts, Kustomize overlays, and FluxCD resources. This page covers its container image (ghcr.io/sophotechlabs/kube-lint-mcp:0.8.9).
Is the io.github.sophotechlabs/kube-lint-mcp server safe to use?
io.github.sophotechlabs/kube-lint-mcp scores 48 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.
What tools does the io.github.sophotechlabs/kube-lint-mcp server expose?
io.github.sophotechlabs/kube-lint-mcp exposes 12 tools: select_kube_context, list_kube_contexts, flux_dryrun, flux_check, flux_status, and 7 more. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.
Is the io.github.sophotechlabs/kube-lint-mcp server still maintained?
io.github.sophotechlabs/kube-lint-mcp 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.