Kubernetes MCP Server

MCP Server for kubernetes management commands

MCP Servers TypeScript Listed MIT

Is Kubernetes MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.6 / 10
Provenance Attested
Signed commits 50%
Last push 9d ago
Advisories None known
Compare Kubernetes MCP Server
Suggest a correction

In detail: Kubernetes MCP Server scores 82.5/100 (Grade A), ranked #119 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.6/10; 50% of recent commits are signed; no published advisory affects its latest release (mcp-server-kubernetes); last pushed 2026-10-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Kubernetes MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Kubernetes MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/Flux159/mcp-server-kubernetes, MIT, last pushed 2026-10-02. 50% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10
  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: mcp-server-kubernetes 4.1.9. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Kubernetes MCP Server.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Kubernetes MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Kubernetes MCP Server compares in MCP Servers

  1. #42 Mnemoverse Memory 82.9 +0.4
  2. #43 Exa MCP Server 82.8 +0.3
  3. #44 Kubernetes MCP Server 82.5 this agent
  4. #45 Slack MCP Server 82.4 −0.1
  5. #46 Esa MCP Server 82.4 −0.1

Bars show each HVTrust score; the tick marks Kubernetes MCP Server’s 82.5.

Where the 82.5 comes from

HVTrust dimensions vs the MCP Servers average

82.5 / 100 · 100.0% confidence

Kubernetes MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.0 / 25
6.6 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.1 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
15.4 / 20
3.2 above avg 12.2
AdoptionLog-scaled stars · package downloads
12.8 / 20
5.4 above avg 7.4

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-11
Rank Moved
Rank rose 26 spots (#145 → #119)
2026-10-01
Rank Moved
Rank dropped 16 spots (#120 → #136)
2026-09-30
Rank Moved
Rank dropped 17 spots (#103 → #120)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.
67.0
Activity sub-score · out of 100
#44

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 04:08 UTC · Repo last pushed 9 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
1.6k
Forks
283
Last Push
2026-10-02
9 days ago
Commits (4 wk)
9
Downloads (7d)
7,058
npm
HN mentions (30d)
—
Open Issues
9
Rank Change
▲26
was #145

Analysis

Activity Inputs

67.0 / 100
StarsRepository reach
19.2 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
12.5 / 25
CommunityFork signal
11.4 / 20

Common questions about Kubernetes MCP Server

Public supply-chain signals for Kubernetes MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Kubernetes MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Kubernetes MCP Server publish package provenance?
Yes. Kubernetes MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Kubernetes MCP Server have an OpenSSF Scorecard?
Kubernetes MCP Server has an OpenSSF Scorecard score of 5.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Kubernetes MCP Server actively maintained?
Maintained. Last push was 9 days ago.
What license does Kubernetes MCP Server use?
Kubernetes MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Kubernetes MCP Server's commits signed?
50% of the last 100 commits to Kubernetes MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Kubernetes MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Kubernetes MCP Server?

For maintainers

HVTrust scores Kubernetes MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 15HVTrust 2Grade 2
2026-10-11
Rank Moved
Rank rose 26 spots (#145 → #119)
2026-10-01
Rank Moved
Rank dropped 16 spots (#120 → #136)
2026-09-30
Rank Moved
Rank dropped 17 spots (#103 → #120)
2026-09-23
Rank Moved
Rank dropped 50 spots (#68 → #118)
2026-09-21
Rank Moved
Rank rose 71 spots (#139 → #68)
2026-09-15
Rank Moved
Rank dropped 24 spots (#107 → #131)
2026-09-14
Rank Moved
Rank rose 11 spots (#118 → #107)
2026-09-11
Rank Moved
Rank dropped 10 spots (#106 → #116)
2026-09-09
Rank Moved
Rank rose 18 spots (#122 → #104)
2026-09-07
Rank Moved
Rank dropped 34 spots (#89 → #123)
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 576 spots (#663 → #87)
2026-09-05
HVTrust Changed
HVTrust up 29.5pts (53.9 → 83.4)
2026-09-04
Rank Moved
Rank dropped 21 spots (#642 → #663)
2026-09-03
Rank Moved
Rank dropped 36 spots (#606 → #642)
2026-09-02
Grade Changed
Trust grade A → C
2026-09-02
Rank Moved
Rank dropped 529 spots (#77 → #606)
2026-09-02
HVTrust Changed
HVTrust down 29.0pts (83.0 → 54.0)
2026-08-30
Rank Moved
Rank rose 15 spots (#90 → #75)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 82.5 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/kubernetes-mcp-server.svg)](https://hvtracker.net/agents/kubernetes-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/kubernetes-mcp-server"><img src="https://hvtracker.net/badge/kubernetes-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON