Ocm MCP Server
Website
An MCP server that lets AI agents operate a multi-cluster Kubernetes fleet through an Open Cluster Management hub, with policy, approval, and audit between the model and your clusters.
Is Ocm MCP Server safe? Strong public trust posture, backed by multiple independent signals.
Compare Ocm MCP Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Ocm MCP Server scores 76.0/100 (Grade B), ranked #253 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 7.3/10; 85% of recent commits are signed; no published advisory affects its latest release (ocm-mcp-server); last pushed 2026-10-31. Every point is earned from checkable signals — never paid placement. How scoring works →
How Ocm 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.
- Raise the OSSF Scorecard from 7.3 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Contributors 0 +3.5 → 79.5 B · #104 of 778
- Sign every commit85% signed today +0.7 → 76.7 B · #140 of 778
Chain of custody
Scanners check what the code says. This traces who ships Ocm 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.
-
Source Signed
github.com/ocm-mcp-server/ocm-mcp-server, Apache-2.0, last pushed 2026-10-31. 85% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 7.3/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases10
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies8
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 10License 10Maintained 10Packaging -1Pinned-Dependencies 8SAST 10Security-Policy 10Signed-Releases 10Token-Permissions 10Vulnerabilities 0 -
Published packages Linked and attested
- PyPI ocm-mcp-server Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: ocm-mcp-server 0.6.0. No published advisory affects it (OSV, checked 2026-11-09).
Changes to this chain
- 2026-10-28 License classification changed from unlicensed to open
- 2026-10-28 Provenance drift warning cleared (now: match)
- 2026-09-23 Package-provenance drift warning: package metadata no longer clearly points at this repo
- 2026-09-23 Package provenance attestation detected
- 2026-09-03 License classification changed from open to unlicensed
- 2026-09-03 Package-provenance drift warning: package metadata no longer clearly points at this repo
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 Ocm 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 Ocm MCP Server compares in MCP Servers
- #144 NotebookLM MCP 76.2 +0.2
- #145 Atlassian Dc MCP 76.1 +0.1
- #146 Ocm MCP Server 76.0 this agent
- #147 Testrail MCP Server 75.9 −0.1
- #148 Mikrotik MCP 75.8 −0.2
Bars show each HVTrust score; the tick marks Ocm MCP Server’s 76.0.
Where the 76.0 comes from
HVTrust dimensions vs the MCP Servers average
76.0 / 100 · 100.0% confidenceOcm MCP Server MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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
Activity & Reach
Analysis
Activity Inputs
34.0 / 100Common questions about Ocm MCP Server
Does Ocm MCP Server publish package provenance?
Does Ocm MCP Server have an OpenSSF Scorecard?
Is Ocm MCP Server actively maintained?
What license does Ocm MCP Server use?
Are Ocm MCP Server's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Ocm 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.
Maintain Ocm MCP Server?
For maintainers
HVTrust scores Ocm 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/ocm-mcp-server)
<a href="https://hvtracker.net/agents/ocm-mcp-server"><img src="https://hvtracker.net/badge/ocm-mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON