Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KubeDrive

MCPB · KUBEDRIVE-0.6.6.MCPB

Your Kubernetes clusters for AI agents through the KubeDrive desktop app, without a kubeconfig.

37 Trust /100

Last scanned (23 hours ago)

Scores higher than 71% of MCPB servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency32
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (SEE LICENSE IN https://github.com/aleksskoz/kubedrive/blob/main/LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3093 tokens (~118/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

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.

Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1
    • Stability: 0.00 → unverified ▼ security
  • 30 Oct 26 34

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Analysed mcpb/https://github.com/aleksskoz/kubedrive/releases/download/v0.6.6/kubedrive-0.6.6.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 26 exposed · ~3,026 tokens

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 →

Tool Tokens
apply ~170

Changes an object to match the manifest (kubectl apply on one object): a server-side dry run first, then the user sees the diff in KubeDrive and allows or declines. The manifest is the whole object as get_resource returns it, edited; fields left out are removed.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
manifeststringyesthe object's full YAML
namestringyesobject name
namespacestring–namespace; empty for all namespaces or cluster-scoped types
reasonstring–why, in one line; the user sees it with the change
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

broken_links ~120

Links between objects that lead nowhere, as KubeDrive's map shows them: Ingress rules to a missing Service or port, Services that select no pods, pods that mount or read a ConfigMap, Secret or PVC that does not exist, autoscalers whose target is gone, disruption budgets that match no pods. Optional references are not judged, nor kinds the user may not list.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
namespacestring–namespace; empty for all namespaces (slower on big clusters)

No output schema declared.

No examples provided.

check_access ~126

Whether the user may do a verb on a type (kubectl auth can-i), by SelfSubjectAccessReview.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
namestring–object name
namespacestring–namespace; empty for all namespaces or cluster-scoped types
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)
verbstringyesget, list, watch, create, update, patch, delete…

No output schema declared.

No examples provided.

cluster_problems ~59

What needs attention, as KubeDrive's cluster overview shows it: failing pods and workloads, nodes not ready, failed Helm releases, and the last hour's warning events.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters

No output schema declared.

No examples provided.

cordon ~64

Marks a node unschedulable, after the user allows it.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
nodestringyes–
reasonstring–why, in one line; the user sees it with the change

No output schema declared.

No examples provided.

delete ~147

Deletes one object after the user allows it in KubeDrive; namespaces and cluster-scoped objects always need the name typed by the user.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
forceboolean–no grace period
namestringyesobject name
namespacestring–namespace; empty for all namespaces or cluster-scoped types
propagationstring––
reasonstring–why, in one line; the user sees it with the change
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

diagnose ~175

Why an object is unhealthy, by KubeDrive's rules (no AI): each finding with severity, the cause, the evidence (cluster messages, the crashed container's last log lines) and a suggested fix. Types: pods, deployments.apps, statefulsets.apps, daemonsets.apps, replicasets.apps, jobs.batch, services, ingresses.networking.k8s.io, persistentvolumeclaims, nodes. Start here before reading logs and events by hand.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
namestringyesobject name
namespacestring–namespace; empty for all namespaces or cluster-scoped types
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

drain ~125

Cordons a node and evicts its pods (kubectl drain; DaemonSet pods stay), after the user allows it. Pods with emptyDir volumes or without a controller are skipped unless the options say otherwise.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
delete_emptydir_databoolean––
forceboolean–also evict pods no controller will recreate
nodestringyes–
reasonstring–why, in one line; the user sees it with the change
timeout_secondsinteger––

No output schema declared.

No examples provided.

exec ~150

Runs one command (an argument list, no shell) in a container without a terminal, after the user allows it: stdout, stderr and the exit code come back, each output cut at 256 KB. Up to 60 seconds.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
commandarrayyesthe program and its arguments, e.g. ["nginx","-T"]
containerstring–needed when the pod has several
namespacestringyesnamespace; empty for all namespaces or cluster-scoped types
podstringyes–
reasonstring–why, in one line; the user sees it with the change

No output schema declared.

No examples provided.

get_events ~103

Events of one object (type and name), or of a namespace (or all namespaces), newest first.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
limitinteger–default 200
namestring–object name
namespacestring–namespace; empty for all namespaces or cluster-scoped types
typestring–with name: events of that object
warnings_onlyboolean––

No output schema declared.

No examples provided.

get_logs ~109

The last lines of a pod's container log, with timestamps. Secret-looking values are redacted.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
containerstring–needed when the pod has several
containsstring–only lines containing this text
namespacestringyes–
podstringyes–
previousboolean–the log of the run before the last restart
tail_linesinteger–default 200

No output schema declared.

No examples provided.

get_resource ~111

One object as YAML, without managedFields. Secret values are removed; credential-looking fields, env values and strings are masked (best effort).

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
namestringyesobject name
namespacestring–namespace; empty for all namespaces or cluster-scoped types
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

list_clusters ~33

Kubernetes clusters (kubeconfig contexts) the user shared with agents in KubeDrive, with API server and default namespace.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_resource_types ~59

Resource types the cluster serves: type id, kind, whether namespaced. Use the ids with the other tools.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
filterstring–substring of id or kind

No output schema declared.

No examples provided.

list_resources ~137

Objects of a type, as kubectl get shows them (server-side columns), one per line.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
field_selectorstring–e.g. status.phase=Running
label_selectorstring–e.g. app=web,tier!=db
limitinteger–default 500
namespacestring–namespace; empty for all namespaces or cluster-scoped types
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

port_forward ~180

Forwards a local port on this computer to a pod, service or workload, after the user allows it; returns the local port and the forward's id (port_forward_stop closes it). The forward stays open until stopped or KubeDrive quits.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
local_portinteger–omit for a free one
namestringyesobject name
namespacestringyesnamespace; empty for all namespaces or cluster-scoped types
portintegeryesthe port in the pod or service
reasonstring–why, in one line; the user sees it with the change
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

port_forward_stop ~33

Closes a port forward opened by port_forward, by its id. No confirmation.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

restart ~128

Rolls out new pods for a Deployment, StatefulSet or DaemonSet (kubectl rollout restart), after the user allows it.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
namestringyesobject name
namespacestringyesnamespace; empty for all namespaces or cluster-scoped types
reasonstring–why, in one line; the user sees it with the change
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

rightsizing ~133

Compares what the cluster's containers request with what they used, from Prometheus (KubeDrive Pro): workloads at risk (killed for memory, throttled by a CPU limit, no requests, using more than they request) and over-requested ones, each container with current and suggested requests and limits (CPU from the 95th percentile, memory from the highest use, plus the user's headroom). Read only; set resources with the edit tools.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
windowstring–how far back to look; default 7d

No output schema declared.

No examples provided.

rollback ~151

Returns a Deployment, StatefulSet or DaemonSet to an earlier revision (kubectl rollout undo); without a revision, the previous one. The user allows it in KubeDrive.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
namestringyesobject name
namespacestringyesnamespace; empty for all namespaces or cluster-scoped types
reasonstring–why, in one line; the user sees it with the change
revisioninteger–omit for the previous revision
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

scale ~132

Sets the replicas of a Deployment, StatefulSet or ReplicaSet, after the user allows it in KubeDrive.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
namestringyesobject name
namespacestringyesnamespace; empty for all namespaces or cluster-scoped types
reasonstring–why, in one line; the user sees it with the change
replicasintegeryes–
typestringyesresource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)

No output schema declared.

No examples provided.

timeline ~228

What changed before it broke: one feed, newest first, of the cluster's events, rollouts (new ReplicaSet revisions with the image that changed), container restarts with exit codes, changes made through KubeDrive with who made them, Helm revisions and firing alerts. With type and name: that object and what it is joined to; without: the whole cluster. Start here for "what happened" and "why did it break". Windows beyond 1h need KubeDrive Pro.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
linkedboolean–include the objects it is joined to (pods, Services, Ingresses, ConfigMaps, autoscaler); default true
namestring–object name
namespacestring–namespace; empty for all namespaces or cluster-scoped types
typestring–resource type id: "pods", "deployments.apps", "ingresses.networking.k8s.io" (list_resource_types)
windowstring–how far back; default 1h

No output schema declared.

No examples provided.

top ~76

CPU (millicores) and memory of pods or nodes from metrics-server, busiest first.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
kindstringyes–
limitinteger–default 50
namespacestring–namespace; empty for all namespaces or cluster-scoped types

No output schema declared.

No examples provided.

trigger_cronjob ~94

Creates a Job from a CronJob right away, after the user allows it; returns the Job's name.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
namestringyesobject name
namespacestringyesnamespace; empty for all namespaces or cluster-scoped types
reasonstring–why, in one line; the user sees it with the change

No output schema declared.

No examples provided.

uncordon ~65

Marks a node schedulable again, after the user allows it.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
nodestringyes–
reasonstring–why, in one line; the user sees it with the change

No output schema declared.

No examples provided.

upgrade_check ~118

What breaks when the cluster moves to a newer Kubernetes minor version (KubeDrive Pro): Helm releases and kubectl-applied manifests that name removed API versions, clients still calling them, kinds removed with no successor, and nodes whose kubelet is too old. Each finding says what to write instead. Read only.

NameTypeReqDescription
clusterstringyeskubeconfig context name, from list_clusters
targetinteger–the minor version of 1.x to check, e.g. 33 for 1.33; default the next one

No output schema declared.

No examples provided.

Install

How do I install the KubeDrive MCP server?

KubeDrive ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 0d96927e9d9821a86e143e1c0b2d283d903705ec08d1c16ebe0161f0cc2fb0c5; the commands to do that are on this page. If it does not match, do not open it.

mcpb · kubedrive-0.6.6.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

0d96927e9d9821a86e143e1c0b2d283d903705ec08d1c16ebe0161f0cc2fb0c5

macOS / Linux

echo "0d96927e9d9821a86e143e1c0b2d283d903705ec08d1c16ebe0161f0cc2fb0c5  kubedrive-0.6.6.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\kubedrive-0.6.6.mcpb).Hash -eq "0d96927e9d9821a86e143e1c0b2d283d903705ec08d1c16ebe0161f0cc2fb0c5"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the KubeDrive MCP server?

KubeDrive is an MCP server listed in the public MCP registry as io.github.aleksskoz/kubedrive. Your Kubernetes clusters for AI agents through the KubeDrive desktop app, without a kubeconfig. This page covers its MCPB bundle (https://github.com/aleksskoz/kubedrive/releases/download/v0.6.6/kubedrive-0.6.6.mcpb).

Is the KubeDrive MCP server safe to use?

KubeDrive scores 37 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 KubeDrive MCP server expose?

KubeDrive exposes 26 tools: list_clusters, list_resource_types, list_resources, get_resource, get_events, and 21 more. Their descriptions and schemas cost roughly 3,026 tokens of context every time the server is loaded.