updated 2026-11-10 04:07 UTC

Containers Kubernetes MCP Server

Repository

Model Context Protocol (MCP) server for Kubernetes and OpenShift

MCP Servers Go Listed Apache-2.0

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

OSSF Scorecard 5.6 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Containers Kubernetes MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Containers Kubernetes MCP Server scores 89.7/100 (Grade A), ranked #35 of 1374 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; 100% of recent commits are signed; no published advisory affects its latest release (kubernetes-mcp-server, kubernetes-mcp-server); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Containers 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Containers 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 Signed

    github.com/containers/kubernetes-mcp-server, Apache-2.0, last pushed 2026-11-10. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review9
    • Branch Protection5
    • Signed Releases0
    • Dangerous Workflow0
    • Token Permissions0
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 9
    Contributors 10
    Dangerous-Workflow 0
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 8
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 6

  3. Published packages Partly attested

  4. What you install today No known advisories

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

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-01 OSSF Scorecard: 4.8/10

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 Containers 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.

Signed credential (JSON) How to verify

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 Containers Kubernetes MCP Server compares in MCP Servers

  1. #6 Easyeda MCP Pro 89.7 ±0
  2. #7 Firecrawl MCP Server 89.7 ±0
  3. #8 Containers Kubernetes MCP Server 89.7 this agent
  4. #9 Apify MCP Server 89.7 ±0
  5. #10 SearXNG Search 88.7 −1.0

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

Where the 89.7 comes from

HVTrust dimensions vs the MCP Servers average

89.7 / 100 · 100.0% confidence

Containers Kubernetes MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.5 / 25
8.7 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.0 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
14.5 / 20
6.9 above avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-11-10
Rank Moved
Rank rose 21 spots (#56 → #35)
2026-10-27
Rank Moved
Rank dropped 10 spots (#49 → #59)
2026-10-17
Rank Moved
Rank rose 17 spots (#76 → #59)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.
Compare with Codebase Memory MCP
View MCP Servers Report missing data
82.6
Activity sub-score · out of 100
#8
In MCP Servers

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-11-10 04:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
2.2k
Forks
487
Last Push
2026-11-10
today
Commits (4 wk)
118
Downloads (7d)
69,031
npm+pypi
HN mentions (30d)
—
Open Issues
63
Rank Change
▲21
was #56

Analysis

Activity Inputs

82.6 / 100
StarsRepository reach
20.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.5 / 20

Common questions about Containers Kubernetes MCP Server

Public supply-chain signals for Containers Kubernetes MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Containers Kubernetes MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Containers Kubernetes MCP Server publish package provenance?
Yes. Containers 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 Containers Kubernetes MCP Server have an OpenSSF Scorecard?
Containers 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 Containers Kubernetes MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Containers Kubernetes MCP Server use?
Containers Kubernetes MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Containers Kubernetes MCP Server's commits signed?
100% of the last 100 commits to Containers 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.

Compare Containers Kubernetes MCP Server head-to-head

Containers Kubernetes MCP Server vs Codebase Memory MCP → Containers Kubernetes MCP Server vs Playwright MCP → Containers Kubernetes MCP Server vs Mobile MCP →

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
Containers Kubernetes MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency 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
How this surface has changed

Detected changes to Containers Kubernetes MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Containers Kubernetes MCP Server?

For maintainers

HVTrust scores Containers 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 10HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-10
Rank Moved
Rank rose 21 spots (#56 → #35)
2026-10-27
Rank Moved
Rank dropped 10 spots (#49 → #59)
2026-10-17
Rank Moved
Rank rose 17 spots (#76 → #59)
2026-10-14
Rank Moved
Rank rose 13 spots (#92 → #79)
2026-10-09
Rank Moved
Rank dropped 11 spots (#78 → #89)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 610 spots (#693 → #83)
2026-09-23
HVTrust Changed
HVTrust up 54.0pts (31.0 → 85.0)
2026-09-22
Newly Listed
First tracked at rank #693
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 13 spots (#52 → #65)
2026-09-01
Scorecard Added
OSSF Scorecard: 4.8/10
2026-09-01
Grade Changed
Trust grade B → A
2026-09-01
Rank Moved
Rank rose 74 spots (#127 → #53)
2026-09-01
HVTrust Changed
HVTrust up 10.1pts (76.0 → 86.1)
2026-08-31
Rank Moved
Rank dropped 17 spots (#110 → #127)
2026-08-26
Rank Moved
Rank dropped 10 spots (#88 → #98)
GitHub → PyPI: kubernetes-mcp-server npm: kubernetes-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 89.7 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/containers-kubernetes-mcp-server.svg)](https://hvtracker.net/agents/containers-kubernetes-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/containers-kubernetes-mcp-server"><img src="https://hvtracker.net/badge/containers-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) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON