Claude Plugin Kubernetes MCP Server

claude-plugin-kubernetes PyPI v0.2.1

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 4

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([k8s_list_secrets]) and tools that can send data out ([k8s_exec]) are exposed together. An agent can move private data to the sink.

Evidence: sources [k8s_list_secrets] → sinks [k8s_exec]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow k8s_list_secrets → k8s_exec

high Tool "k8s_exec" exposes command/code executionMTC-CAP-001

Tool "k8s_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool k8s_exec

medium Unconstrained command parameter "command" on "k8s_exec"MTC-CAP-006

Tool "k8s_exec" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool k8s_exec · inputSchema.properties.command

low Mutating tool "k8s_exec" declares no destructiveHintMTC-CAP-005

Tool "k8s_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool k8s_exec

Tools 50

Each tool and what it can reach — statically extracted from the published source.

  • k8s_execruns code / shell
  • k8s_list_secretsreads sensitive data
  • k8s_api_resourcesno sensitive capability
  • k8s_apply_manifestno sensitive capability
  • k8s_cluster_infono sensitive capability
  • k8s_delete_podno sensitive capability
  • k8s_delete_resourceno sensitive capability
  • k8s_describeno sensitive capability
  • k8s_diffno sensitive capability
  • k8s_find_issuesno sensitive capability
Show 40 more tools ↓
  • k8s_getno sensitive capability
  • k8s_get_configmap_datano sensitive capability
  • k8s_get_contextsno sensitive capability
  • k8s_get_yamlno sensitive capability
  • k8s_list_configmapsno sensitive capability
  • k8s_list_cronjobsno sensitive capability
  • k8s_list_daemonsetsno sensitive capability
  • k8s_list_deploymentsno sensitive capability
  • k8s_list_eventsno sensitive capability
  • k8s_list_hpano sensitive capability
  • k8s_list_imagesno sensitive capability
  • k8s_list_ingressesno sensitive capability
  • k8s_list_jobsno sensitive capability
  • k8s_list_limitrangesno sensitive capability
  • k8s_list_namespacesno sensitive capability
  • k8s_list_networkpoliciesno sensitive capability
  • k8s_list_nodesno sensitive capability
  • k8s_list_poddisruptionbudgetsno sensitive capability
  • k8s_list_podsno sensitive capability
  • k8s_list_pvcsno sensitive capability
  • k8s_list_pvsno sensitive capability
  • k8s_list_resourcequotasno sensitive capability
  • k8s_list_rolebindingsno sensitive capability
  • k8s_list_rolesno sensitive capability
  • k8s_list_serviceaccountsno sensitive capability
  • k8s_list_servicesno sensitive capability
  • k8s_list_statefulsetsno sensitive capability
  • k8s_list_storageclassesno sensitive capability
  • k8s_logsno sensitive capability
  • k8s_logs_selectorno sensitive capability
  • k8s_node_operationno sensitive capability
  • k8s_patch_resourceno sensitive capability
  • k8s_restart_deploymentno sensitive capability
  • k8s_rollback_deploymentno sensitive capability
  • k8s_rollout_historyno sensitive capability
  • k8s_rollout_statusno sensitive capability
  • k8s_scaleno sensitive capability
  • k8s_self_testno sensitive capability
  • k8s_top_nodesno sensitive capability
  • k8s_top_podsno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.1 latest A 92/100 4 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/claude-plugin-kubernetes/badge.svg)](https://mcptrustchecker.com/registry/claude-plugin-kubernetes)
HTML
<a href="https://mcptrustchecker.com/registry/claude-plugin-kubernetes"><img src="https://mcptrustchecker.com/registry/claude-plugin-kubernetes/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/claude-plugin-kubernetes/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan claude-plugin-kubernetes --online --registry pypi

Use the free API → How scoring works

More in Developer Tools