Is Containers Kubernetes MCP Server safe to use?

Containers Kubernetes MCP Server has an HVTrust score of 85.0/100 (Grade A), ranked #83 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Containers Kubernetes MCP Server?

Containers Kubernetes MCP Server scores 85.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.1k GitHub stars and is categorized under MCP Servers.

Containers Kubernetes MCP Server

containers/kubernetes-mcp-server

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 4.7 / 10

Provenance Attested

Signed commits 100%

Last push yesterday

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 85.0/100 (Grade A), ranked #83 of 1325 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 4.7/10; 100% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Containers Kubernetes MCP Server compares in MCP Servers

#26 Easyeda MCP Pro 85.4 +0.4
#27 Browserstack MCP Server 85.2 +0.2
#28 Containers Kubernetes MCP Server 85.0 this agent
#29 Stripe Agent Toolkit 84.7 −0.3
#30 CloakBrowser MCP 84.5 −0.5

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

Where the 85.0 comes from

HVTrust dimensions vs the MCP Servers average

85.0 / 100 · 100.0% confidence

Containers Kubernetes MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.4 / 25

8.1 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.5 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.7 / 20

5.6 above avg 12.1

AdoptionLog-scaled stars · package downloads

12.4 / 20

5.2 above avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

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

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.7/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent Get email alerts for Containers Kubernetes MCP Server View MCP Servers Report missing data

75.4

Activity sub-score · out of 100

#28

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

2.1k

Forks

441

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

1,889

pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #83

Analysis

Activity Inputs

75.4 / 100

StarsRepository reach

20.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

18.1 / 25

CommunityFork signal

12.3 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.7 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 0

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 6

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 4.7/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.

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

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)

2026-08-08

Newly Listed

First tracked at rank #77

GitHub → PyPI: kubernetes-mcp-server npm: kubernetes-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON