- Reliability 10/20
- The README claims an 'extensive test suite' and the repo carries a build.yaml CI status badge, indicating some CI pipeline exists; the documented tool list is internally consistent with the described feature set with no obvious contradictions. However, this is a static-only review — no test files, coverage, or workflow contents were inspected, and there is no way to verify that any of the three packaging methods (npm, PyPI, OCI) actually complete the MCP init + tool-list handshake in practice. All three packages in server.json carry a placeholder version of '0.0.0', which further undermines confidence that declared behavior matches real, published artifacts. Per the static calibration rule, without verifiable execution evidence the score cannot exceed 12, so this is scored 10.
- Security and permissions 10/20
- By default the server runs in read-write mode and exposes many high-risk operations: pods_exec (arbitrary command execution inside containers), pods_delete, resources_delete, resources_create_or_update (a full server-side-apply overwrite), helm_install/uninstall, resources_scale, and KubeVirt's vm_lifecycle — none of which have a server-enforced confirmation step by default; confirmation is left entirely to the client UI. Mitigations do exist but are opt-in: --read-only, --disable-destructive, a denied_resources TOML blocklist, and OAuth/OIDC support for HTTP mode; the docs also state that tokens, keys, passwords and cloud credentials are automatically redacted before being sent to clients, and a dedicated least-privilege ServiceAccount setup guide is referenced. No red-line issue was found (no malware, no covert exfiltration, no fabricated identity/results), but the broad default permission scope combined with destructive operations enabled by default and no built-in confirmation matches 'main risks visible but permissions/confirmation/scoping incomplete,' scored 10.
- Maintenance 14/20
- The repository belongs to the containers GitHub organization (home to Podman, Buildah, and related projects), is Apache-2.0 licensed, has 1957 stars, is not archived, and shows 93 open issues indicating ongoing community engagement. The docs directory is extensive and appears actively maintained (multiple topic-specific guides, an ecosystem validation table with eval scenario counts). However, all three package entries in server.json use a placeholder version '0.0.0', which either reflects a manifest-generation gap or makes it impossible to confirm actual release cadence and version discipline; no explicit security-response channel or release policy is stated. Given generally positive activity signals offset by governance gaps, scored 14.
- Documentation 17/20
- Documentation coverage is broad: beyond the README there is a dedicated docs/ directory covering configuration reference (configuration.md), observability (OTEL.md), logging (logging.md), custom prompts (prompts.md), OIDC setup guides (Keycloak, Entra ID), client-specific getting-started guides (Claude Code, a secure Kubernetes deployment guide), plus toolset-specific docs (KIALI.md, kubevirt.md, NETOBSERV.md). Tool parameters are auto-generated into clear tables listing each argument. The ecosystem validation table further links to checkable evidence (evals/tasks). The main gap is the absence of a consolidated 'known limitations' or explicitly labeled troubleshooting section. Scored 17.
- Setup experience 12/20
- Concrete configuration examples are provided for multiple mainstream clients (Claude Desktop, VS Code/Insiders, Cursor, Goose CLI, Claude Code), and npx/uvx enable near one-line startup. The Docker/OCI path requires manually mounting the kubeconfig, setting an env var, and mapping a port — documented but more manual. The stated prerequisite of 'access to a Kubernetes cluster' is an inherent domain dependency, not a setup flaw. However, all three packages in server.json list a placeholder version of '0.0.0', meaning a user following the manifest literally cannot be sure which actual version would be fetched — a real risk of setup instructions diverging from a genuinely installable artifact. Per the static calibration rule, without verified execution evidence the setup score cannot exceed 15, so this is scored 12.