4.1.8 → 4.1.9
patch release, 2 October 2026No tool definition changed.
MCP servers / mcp-server-kubernetes
mcp-server-kubernetes
No tool definition changed across the 6 releases that started, up to 4.1.9.
npm package · npm page · recorded on 24 October 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. Method and limits.
Release by release
4.1.7 → 4.1.8
patch release, 29 September 2026No tool definition changed.
4.1.6 → 4.1.7
patch release, 14 September 2026No tool definition changed.
4.1.5 → 4.1.6
patch release, 31 August 2026No tool definition changed.
4.1.4 → 4.1.5
patch release, 31 August 2026No tool definition changed.
Releases tried: 4.1.4 (2026-08-08); 4.1.5 (2026-08-31); 4.1.6 (2026-08-31); 4.1.7 (2026-09-14); 4.1.8 (2026-09-29); 4.1.9 (2026-10-02).
Tools in 4.1.9
The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition.
| Tool | Description | Pin |
|---|---|---|
| cleanup | Cleanup all managed resources | d49de4e77dab |
| kubectl_get | Get or list Kubernetes resources by resource type, name, and optionally namespace | cbbcfce2f9f5 |
| kubectl_describe | Describe Kubernetes resources by resource type, name, and optionally namespace | d0c70fbfdd1b |
| kubectl_apply | Apply a Kubernetes YAML manifest from a string or file | c586f26d9e0c |
| kubectl_delete | Delete Kubernetes resources by resource type, name, labels, or from a manifest file | ebe1544eb524 |
| kubectl_create | Create Kubernetes resources using various methods (from file or using subcommands) | 01a4a129b4fb |
| kubectl_logs | Get logs from Kubernetes resources like pods, deployments, or jobs | be09279ed22d |
| kubectl_scale | Scale a Kubernetes deployment | 1b40a0817a0a |
| kubectl_patch | Update field(s) of a resource using strategic merge patch, JSON merge patch, or JSON patch | ff9fef5dc630 |
| kubectl_rollout | Manage the rollout of a resource (e.g., deployment, daemonset, statefulset) | 6592eed60dbb |
| kubectl_context | Manage Kubernetes contexts - list, get, or set the current context | 1d8c3bc1545e |
| kubectl_reconnect | Reconnect to the Kubernetes API server by recreating all API clients. Use this after cluster upgrades (e.g., EKS control plane upgrades that rotate ENIs/IPs) to force fresh DNS resolution and new TCP connections. | 204fa3b451a5 |
| explain_resource | Get documentation for a Kubernetes resource or field | b823311e4bf0 |
| install_helm_chart | Install a Helm chart with support for both standard and template-based installation | 9208ff198512 |
| upgrade_helm_chart | Upgrade an existing Helm chart release | b1843b686e02 |
| uninstall_helm_chart | Uninstall a Helm chart release | 1c12c74ac17b |
| node_management | Manage Kubernetes nodes with cordon, drain, and uncordon operations | 8f2d54db23a5 |
| port_forward | Forward a local port to a port on a Kubernetes resource | 38b83cf982fc |
| stop_port_forward | Stop a port-forward process | 8bab39e56daf |
| exec_in_pod | Execute a command in a Kubernetes pod or container and return the output. Command must be an array of strings where the first element is the executable and remaining elements are arguments. This executes directly without shell interpretation for security. | c9abcbc816a1 |
| list_api_resources | List the API resources available in the cluster | 81fd77699cd1 |
| kubectl_generic | Execute any kubectl command with the provided arguments and flags | 8b2bba146a5c |
| ping | Verify that the counterpart is still responsive and the connection is alive. | 46b865a4422a |
Lock these tools
Pin what mcp-server-kubernetes serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.
$ pip install verfy
$ verfy lock check --update # shows each tool, then writes verfy.lock
$ git add verfy.lock# .github/workflows/verfy.yml, after actions/checkout
- uses: anvarbekovjavohir277-dot/verfy-action@v1Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.