io.github.sandeepbazar/ocm-mcp-server
OCI · GHCR.IO/SANDEEPBAZAR/OCM-MCP-SERVER:0.4.0 · 2 COMPONENTS · SCANNED SEP 20
Guardrailed fleet ops for AI agents: multi-cluster Kubernetes via OCM with policy, approval, audit.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 37 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2758 tokens (~68/item across 40 items; 35 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.sandeepbazar/ocm-mcp-server server?
io.github.sandeepbazar/ocm-mcp-server runs locally as a container image, launched with docker run --rm -i ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0
claude mcp add sandeepbazar-ocm-mcp-server -- docker run --rm -i ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0
{
"mcpServers": {
"sandeepbazar-ocm-mcp-server": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0"
]
}
}
} {
"servers": {
"sandeepbazar-ocm-mcp-server": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0"
]
}
}
} codex mcp add sandeepbazar-ocm-mcp-server -- docker run --rm -i ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sandeepbazar-ocm-mcp-server": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0"
],
"enabled": true
}
}
} mcp_servers:
sandeepbazar-ocm-mcp-server:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0"] {
"McpServers": {
"sandeepbazar-ocm-mcp-server": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0"
]
}
}
} {
"mcpServers": {
"sandeepbazar-ocm-mcp-server": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_cluster_action ~72
Apply a previously proposed cluster lifecycle action. Requires a human-minted token. Args: proposal_id: id returned by propose_cluster_action. approval_token: token the operator produced with `ocm-mcp approve <id>`.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_token | string | yes | – |
| proposal_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
apply_manifestwork ~72
Apply a previously proposed ManifestWork. Requires a human-minted approval token. Args: proposal_id: id returned by propose_manifestwork. approval_token: token the operator produced with `ocm-mcp approve <id>`.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_token | string | yes | – |
| proposal_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_addon_health ~29
Per-cluster add-on health across the fleet (ManagedClusterAddOn Available / Degraded).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_audit_trail ~90
Return the last N entries of this server's own tool-call audit log. Args: last_n: number of trailing audit entries to return (default 30). Use this at the end of an incident to write an accurate post-incident report of what was inspected, proposed, approved, and applied - from the record, not from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| last_n | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_cluster ~70
Full view of one ManagedCluster. Args: cluster: managed cluster name as the hub knows it (see list_clusters). Returns acceptance (hubAcceptsClient), taints, hub conditions, Kubernetes version, capacity/allocatable, and the cluster's ClusterClaims.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_cluster_health ~69
Health summary for one cluster: hub conditions, unhealthy pods, degraded deployments. Args: cluster: managed cluster name. Pod/deployment detail requires a read-only spoke context (OCM_MCP_SPOKE_CONTEXTS); hub conditions work without one.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_cluster_info ~97
Extended inventory for one cluster from the hub: OpenShift version, nodes, console URL. Args: cluster: managed cluster name. Reads ManagedClusterInfo on the hub, so it needs no spoke access and works for any spoke - external OpenShift, HCP, or cloud. Needs the ACM/MCE multicloud-operators-foundation add-on; reports clearly if it is not present.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_fleet_health ~108
Health of the WHOLE fleet in one call: hub conditions for every cluster plus concurrent pod/deployment scans of each spoke that has a read context. Args: clusters: optional comma-separated managed-cluster names to scope the sweep; empty means every cluster on the hub. Clusters with problems sort first. A broken spoke shows an 'error' entry instead of failing the sweep. Prefer this over calling get_cluster_health in a loop.
| Name | Type | Req | Description |
|---|---|---|---|
| clusters | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_hosted_cluster ~61
Detailed HostedCluster: version, conditions, and its NodePools. Args: name: HostedCluster name. namespace: the namespace the HostedCluster lives in (its hosting namespace).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| namespace | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_manifestwork ~86
Detailed ManifestWork status: top-level conditions and per-resource status feedback. Args: cluster: managed cluster name. name: ManifestWork name. Use this to answer 'why is this ManifestWork not Applied/Available' and to read status feedback (for example replica counts) reported back from the spoke.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_placement_decision ~56
Which clusters a Placement actually selected (reads its PlacementDecisions). Args: placement: Placement name. namespace: the namespace the Placement lives in.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | – |
| placement | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_pod_logs ~115
Tail logs from a pod on a managed cluster. Args: cluster: managed cluster name. namespace: pod namespace. pod: pod name. container: container name; empty picks the default container. lines: number of trailing log lines (default 80). Falls back to the previous container instance if the current one is crashing.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| container | string | – | – |
| lines | integer | – | – |
| namespace | string | yes | – |
| pod | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_resource ~107
Generic get of one allow-listed OCM resource, in full. Args: resource: an OCM resource type (see list_resources for the allow-list). name: object name. namespace: required for namespaced types (usually the cluster namespace). Never returns a Secret: Secrets are not on the allow-list, so this capability does not exist rather than being merely restricted.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| namespace | string | – | – |
| resource | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_addon_placement_scores ~52
List AddOnPlacementScores in a cluster's namespace (custom scores prioritizers consume). Args: cluster: managed cluster name (its hub namespace holds the scores).
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_addons_for_cluster ~46
Every add-on installed on one cluster, with health (ManagedClusterAddOn in its namespace). Args: cluster: managed cluster name.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cluster_claims ~29
Every cluster's ClusterClaims (id, platform, region, version) rolled up from status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cluster_management_addons ~28
List fleet-level add-on definitions (ClusterManagementAddOn) and their install strategy.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cluster_set_bindings ~52
List ManagedClusterSetBindings (which ClusterSets a namespace's Placements may use). Args: namespace: limit to one namespace; empty lists bindings across all namespaces.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cluster_sets ~21
List ManagedClusterSets with their selector type and member clusters.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_clusters ~22
List all managed clusters with availability, version, labels, and capacity.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_hosted_clusters ~97
List HyperShift HostedClusters, when the hub is the HCP hosting cluster. Args: namespace: limit to one namespace; empty lists across all namespaces. HostedCluster objects live on whichever cluster hosts the control plane. If your HCPs are hosted on a separate management cluster, they are not on this hub - this reports that clearly, and the spokes still appear via list_clusters.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_manifestworkreplicasets ~53
List ManifestWorkReplicaSets (a template fanned across a Placement) with rollout summary. Args: namespace: limit to one namespace; empty lists across all namespaces.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_manifestworks ~39
List ManifestWorks targeting a cluster (what the hub is managing there). Args: cluster: managed cluster name.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_node_pools ~69
List HyperShift NodePools (worker groups), optionally filtered to one HostedCluster. Args: namespace: limit to one namespace; empty lists across all namespaces. cluster: optional HostedCluster name to filter node pools by.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | – | – |
| namespace | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_pending_csrs ~25
List pending cluster-join / add-on registration CSRs awaiting hub approval.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_pending_proposals ~24
List proposals (ManifestWorks and cluster actions) waiting for human approval.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_placements ~43
List Placements and how many clusters each currently selects. Args: namespace: limit to one namespace; empty lists across all namespaces.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_policies ~49
List governance Policies and per-cluster compliance (only if the add-on is installed). Args: namespace: limit to one namespace; empty lists across all namespaces.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_policy_violations ~30
Only the NonCompliant / Pending Policy-cluster pairs across the fleet - the open risks.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_resources ~132
Generic list over an allow-list of OCM API types (identity + conditions only). Args: resource: an OCM resource type, e.g. managedclusters, placements, placementdecisions, manifestworks, managedclusteraddons, clustermanagementaddons, managedclustersets, policies, klusterlets. namespace: for namespaced types, limit to one namespace; empty lists all. Only Open Cluster Management types are allowed. Secrets and other credential resources are not on the allow-list and cannot be read through this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | – | – |
| resource | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
propose_cluster_action ~246
Propose an OCM cluster lifecycle action. Does NOT apply anything. Args: cluster: target managed cluster name. action: one of 'cordon' (taint out of scheduling), 'uncordon' (undo cordon), 'set_label' (params: {"key","value"}; empty value removes the label), 'accept' (set hubAcceptsClient=true and approve pending join CSRs), 'enable_addon' (params: {"addon","install_namespace"?}; create a ManagedClusterAddOn), 'disable_addon' (params: {"addon"}; delete it). summary: one or two sentences the human approver will read. params_json: JSON object of action parameters (set_label and the addon actions need it; cordon/uncordon/accept do not). The action is validated with a server-side dry-run, then stored pending. The human operator must run `ocm-mcp approve <id>` to mint the approval token.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| cluster | string | yes | – |
| params_json | string | – | – |
| summary | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
propose_manifestwork ~174
Propose a change to one cluster as an OCM ManifestWork. Does NOT apply anything. Args: cluster: target managed cluster name. name: a short kebab-case name for the ManifestWork. summary: one or two sentences a human approver will read. Be precise about what changes and why. manifests_json: JSON array of complete Kubernetes manifests (allowed kinds only; all namespaced; images pinned). The proposal must pass static guardrails and a Kyverno dry-run on the hub. On success it is stored pending and the human operator must run `ocm-mcp approve <id>` to mint an approval token.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| manifests_json | string | yes | – |
| name | string | yes | – |
| summary | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
propose_rollback ~101
Propose rolling back an applied ManifestWork. Applies nothing; needs its own approval. Args: proposal_id: id of an already-applied ManifestWork proposal. Creates a distinct rollback proposal bound to the exact ManifestWork name and UID. The human approves it separately (`ocm-mcp approve <rollback-id>`), and the token can only authorize a rollback - an old apply token can never delete a workload.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
query_events ~87
Recent Kubernetes events from a managed cluster, newest first. Args: cluster: managed cluster name. namespace: optional namespace filter; empty means all namespaces. limit: maximum number of events to return (default 40). Use this to find the 'why' behind unhealthy pods.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | yes | – |
| limit | integer | – | – |
| namespace | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rollback_manifestwork ~73
Delete a ManifestWork after a rollback proposal has been approved. Args: rollback_proposal_id: id returned by propose_rollback. approval_token: a rollback token from `ocm-mcp approve <rollback-id>`.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_token | string | yes | – |
| rollback_proposal_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.sandeepbazar/ocm-mcp-server server?
io.github.sandeepbazar/ocm-mcp-server is listed in the public MCP registry as io.github.sandeepbazar/ocm-mcp-server. Guardrailed fleet ops for AI agents: multi-cluster Kubernetes via OCM with policy, approval, audit. This page covers its container image (ghcr.io/sandeepbazar/ocm-mcp-server:0.4.0).
Is the io.github.sandeepbazar/ocm-mcp-server server safe to use?
io.github.sandeepbazar/ocm-mcp-server scores 52 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.sandeepbazar/ocm-mcp-server server expose?
io.github.sandeepbazar/ocm-mcp-server exposes 35 tools: list_clusters, get_cluster, list_cluster_sets, list_cluster_set_bindings, list_cluster_claims, and 30 more. Their descriptions and schemas cost roughly 2,524 tokens of context every time the server is loaded.
Is the io.github.sandeepbazar/ocm-mcp-server server still maintained?
io.github.sandeepbazar/ocm-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.sandeepbazar/ocm-mcp-server server under?
io.github.sandeepbazar/ocm-mcp-server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.