kubelint-mcp
Related Servers
Alternatives to kubelint-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables agents and users to validate Kubernetes manifests (YAML/JSON, multi-document) against the API of a chosen Kubernetes version without needing a cluster. It reports removed or deprecated APIs with replacements, unknown or misspelt fields, misconfigurations the API server would reject, Pod Security Standard violations, and common risks, each with file, line, and fix.31MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to statically lint and explain Dockerfiles, compose files, and .dockerignore rules with line-numbered findings, concrete fixes, layer-cache analysis, multi-stage suggestions, and safe fix previews, all without a Docker daemon.7MIT
- AlicenseAqualityCmaintenanceEnables AI agents to audit Kubernetes manifests for configuration traps that pass linters but silently break production, via read-only tools to audit YAML, list known traps, and explain trap details.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to run static analysis on GitHub repositories, raw code snippets, or local directories to detect cloud cost leaks in Terraform/AWS configs, PostgreSQL migration table-lock hazards, and OWASP/Next.js API security gaps. Each finding returns structured severity, line-level detail, and drop-in fixes.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI to statically lint Dockerfiles and compose files without Docker by parsing their true structure, reporting line-numbered findings with concrete fixes, and analyzing cache order, .dockerignore matching, and safe fix previews as diffs.MIT
- AlicenseAqualityCmaintenanceEnables deterministic, offline diagnosis of Kubernetes and container failures, generation of exact YAML/Dockerfile fixes, secret and PII redaction, and zero-trust policy checks for agent-proposed commands.5MIT
TDQS
Scored across 8 tools
Each tool targets a clearly distinct layer of the workflow: inventory (k8s_overview), per-object rules (lint_manifests), cross-object rules (check_references), RBAC (rbac_review), single-object explanation (explain_resource), remediation (suggest_fixes), chart inputs (values_review) and chart rendering (render_helm). The descriptions actively disambiguate the risky pairs ('Cross-object checks are in check_references', 'use render_helm ... with lint_manifests' for rendered output vs values_review for inputs).
All names are snake_case and readable, but the pattern mixes verb_noun (lint_manifests, check_references, explain_resource, suggest_fixes, render_helm) with noun_noun/qualifier forms (k8s_overview, rbac_review, values_review). The deviation is minor and each name still predicts its action.
Eight tools is well within the sweet spot and every tool covers a non-redundant stage of the static-analysis workflow, from inspection through linting to fix suggestions. Nothing feels padded or missing purely for count's sake.
The surface covers CRUD-equivalent lifecycle for the domain: overview, per-object and cross-object linting, RBAC, explanation, mechanical fixes, and Helm values/render paths, including an opt-in exec guard. Minor gaps remain — no kustomize/overlay rendering and no aggregate multi-file report output — but agents can work around them with directory inputs.