
Kubernetes Manifest Audit
Wraps kube-linter in an MCP interface so you can audit Kubernetes manifests from Claude or any other MCP client. You get four tools: audit a single YAML string, audit multiple files at once, list all 63 available checks, and explain specific findings. The server returns structured reports with severity levels, check IDs, categories like security and RBAC, plus remediation hints. It catches privileged containers, missing resource limits, weak RBAC wildcards, absence of probes, and dozens more issues across Deployments, Services, StatefulSets, NetworkPolicies, and the rest of the Kubernetes API surface. Hosted on Apify with pay per call pricing, two cents per audit. Built by Unbearable Labs for shift left scanning without leaving your agent workflow.
- tools
- 4
- auth
- Secret needed
- transport
- HTTP
- last updated
- Jun 2, 2026
Tools
4 toolsPublic tool metadata for what this MCP can expose to an agent.
audit_manifestAudit a single YAML string (may contain multi-doc `---`).
Audit a single YAML string (may contain multi-doc `---`).
No parameter schema in public metadata yet.
audit_directoryAudit multiple files — cross-file checks work correctly.
Audit multiple files — cross-file checks work correctly.
No parameter schema in public metadata yet.
list_checksBrowse the full 63-check catalog with severity + category.
Browse the full 63-check catalog with severity + category.
No parameter schema in public metadata yet.
explain_checkGet description + remediation for one specific check.
Get description + remediation for one specific check.
No parameter schema in public metadata yet.
Sponsors
Readme
k8s-manifest-audit
k8s-manifest-audit — static audit of Kubernetes manifests via MCP. Powered by kube-linter. Part of the Unbearable Labs audit shop.
Built by Unbearable Labs. Pay-per-event pricing — only billed when a tool is actually called.
What it does
Point any MCP-capable client (Claude Desktop, Cursor, n8n, Make, Zapier, custom agents) at this server, hand it a Kubernetes manifest or directory of manifests, get back a structured report:
- Severity — high / medium / low / info
- Check ID — kube-linter check name (e.g.
privileged-container,unset-cpu-requirements) - Category — security / resources / availability / network / rbac / images / config
- Message — what kube-linter found and where
- Remediation hint — what to do about it
- Object location — kind, name, namespace of the offending resource
63 checks total (31 enabled by default). Covers Deployment, Service, Ingress, ConfigMap, Secret, StatefulSet, DaemonSet, Job, CronJob, NetworkPolicy, RBAC, HPA, PDB, and more.
Tools
Details
- Repository
- github.com/unbearabledev/k8s-manifest-audit
- Categories
- Cloud & Infrastructure, Developer Tools, Security & Pentesting
- Transport
- HTTP
- Auth
- Required
- Registry
- MCP registry, active