# io.github.ocm-mcp-server/ocm-mcp-server (oci · ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0)

Guardrailed fleet ops for AI agents: multi-cluster Kubernetes via OCM with policy, approval, audit.

- Trust score: 51/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0`: 51/100 (this document), [markdown](https://verifymcp.io/servers/ocm-mcp-server-ocm-mcp-server/ghcr-io-ocm-mcp-server-ocm-mcp-server-0-6-0.md), [page](https://verifymcp.io/servers/ocm-mcp-server-ocm-mcp-server/ghcr-io-ocm-mcp-server-ocm-mcp-server-0-6-0)
- pypi · `ocm-mcp-server`: 64/100, [markdown](https://verifymcp.io/servers/ocm-mcp-server-ocm-mcp-server/ocm-mcp-server.md), [page](https://verifymcp.io/servers/ocm-mcp-server-ocm-mcp-server/ocm-mcp-server)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 21 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2758 tokens (~68/item across 40 items; 35 tools + 5 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

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

## Install

### How do I install the io.github.ocm-mcp-server/ocm-mcp-server server?

io.github.ocm-mcp-server/ocm-mcp-server runs locally as a container image, launched with docker run --rm -i ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ocm-mcp-server-ocm-mcp-server -- docker run --rm -i ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0
```

### Cursor

```json
{
  "mcpServers": {
    "ocm-mcp-server-ocm-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ocm-mcp-server-ocm-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ocm-mcp-server-ocm-mcp-server -- docker run --rm -i ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ocm-mcp-server-ocm-mcp-server": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  ocm-mcp-server-ocm-mcp-server:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "ocm-mcp-server-ocm-mcp-server": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "ocm-mcp-server-ocm-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/ocm-mcp-server/ocm-mcp-server:0.6.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 46, +5)

- [functional improvement] Stability: unverified → 0.30

### 2026-08-29 (score 41)

First indexed and scored.

## MCP tools (35)

### `list_clusters` (~22 tokens)

List all managed clusters with availability, version, labels, and capacity.

Output parameters:

- `result` (string)

### `get_cluster` (~70 tokens)

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.

Input parameters:

- `cluster` (string, required)

Output parameters:

- `result` (string)

### `list_cluster_sets` (~21 tokens)

List ManagedClusterSets with their selector type and member clusters.

Output parameters:

- `result` (string)

### `list_cluster_set_bindings` (~52 tokens)

List ManagedClusterSetBindings (which ClusterSets a namespace's Placements may use).

Args:
    namespace: limit to one namespace; empty lists bindings across all namespaces.

Input parameters:

- `namespace` (string)

Output parameters:

- `result` (string)

### `list_cluster_claims` (~29 tokens)

Every cluster's ClusterClaims (id, platform, region, version) rolled up from status.

Output parameters:

- `result` (string)

### `get_cluster_info` (~97 tokens)

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.

Input parameters:

- `cluster` (string, required)

Output parameters:

- `result` (string)

### `get_cluster_health` (~69 tokens)

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.

Input parameters:

- `cluster` (string, required)

Output parameters:

- `result` (string)

### `get_fleet_health` (~108 tokens)

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.

Input parameters:

- `clusters` (string)

Output parameters:

- `result` (string)

### `query_events` (~87 tokens)

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.

Input parameters:

- `cluster` (string, required)
- `limit` (integer)
- `namespace` (string)

Output parameters:

- `result` (string)

### `get_pod_logs` (~115 tokens)

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.

Input parameters:

- `cluster` (string, required)
- `container` (string)
- `lines` (integer)
- `namespace` (string, required)
- `pod` (string, required)

Output parameters:

- `result` (string)

### `list_placements` (~43 tokens)

List Placements and how many clusters each currently selects.

Args:
    namespace: limit to one namespace; empty lists across all namespaces.

Input parameters:

- `namespace` (string)

Output parameters:

- `result` (string)

### `get_placement_decision` (~56 tokens)

Which clusters a Placement actually selected (reads its PlacementDecisions).

Args:
    placement: Placement name.
    namespace: the namespace the Placement lives in.

Input parameters:

- `namespace` (string, required)
- `placement` (string, required)

Output parameters:

- `result` (string)

### `list_addon_placement_scores` (~52 tokens)

List AddOnPlacementScores in a cluster's namespace (custom scores prioritizers consume).

Args:
    cluster: managed cluster name (its hub namespace holds the scores).

Input parameters:

- `cluster` (string, required)

Output parameters:

- `result` (string)

### `list_manifestworks` (~39 tokens)

List ManifestWorks targeting a cluster (what the hub is managing there).

Args:
    cluster: managed cluster name.

Input parameters:

- `cluster` (string, required)

Output parameters:

- `result` (string)

### `get_manifestwork` (~86 tokens)

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.

Input parameters:

- `cluster` (string, required)
- `name` (string, required)

Output parameters:

- `result` (string)

### `list_manifestworkreplicasets` (~53 tokens)

List ManifestWorkReplicaSets (a template fanned across a Placement) with rollout summary.

Args:
    namespace: limit to one namespace; empty lists across all namespaces.

Input parameters:

- `namespace` (string)

Output parameters:

- `result` (string)

### `propose_manifestwork` (~174 tokens)

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.

Input parameters:

- `cluster` (string, required)
- `manifests_json` (string, required)
- `name` (string, required)
- `summary` (string, required)

Output parameters:

- `result` (string)

### `apply_manifestwork` (~72 tokens)

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

Input parameters:

- `approval_token` (string, required)
- `proposal_id` (string, required)

Output parameters:

- `result` (string)

### `propose_rollback` (~101 tokens)

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.

Input parameters:

- `proposal_id` (string, required)

Output parameters:

- `result` (string)

### `rollback_manifestwork` (~73 tokens)

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

Input parameters:

- `approval_token` (string, required)
- `rollback_proposal_id` (string, required)

Output parameters:

- `result` (string)

### `list_cluster_management_addons` (~28 tokens)

List fleet-level add-on definitions (ClusterManagementAddOn) and their install strategy.

Output parameters:

- `result` (string)

### `get_addon_health` (~29 tokens)

Per-cluster add-on health across the fleet (ManagedClusterAddOn Available / Degraded).

Output parameters:

- `result` (string)

### `list_addons_for_cluster` (~46 tokens)

Every add-on installed on one cluster, with health (ManagedClusterAddOn in its namespace).

Args:
    cluster: managed cluster name.

Input parameters:

- `cluster` (string, required)

Output parameters:

- `result` (string)

### `list_pending_csrs` (~25 tokens)

List pending cluster-join / add-on registration CSRs awaiting hub approval.

Output parameters:

- `result` (string)

### `propose_cluster_action` (~246 tokens)

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.

Input parameters:

- `action` (string, required)
- `cluster` (string, required)
- `params_json` (string)
- `summary` (string, required)

Output parameters:

- `result` (string)

### `apply_cluster_action` (~72 tokens)

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

Input parameters:

- `approval_token` (string, required)
- `proposal_id` (string, required)

Output parameters:

- `result` (string)

### `list_policies` (~49 tokens)

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.

Input parameters:

- `namespace` (string)

Output parameters:

- `result` (string)

### `list_policy_violations` (~30 tokens)

Only the NonCompliant / Pending Policy-cluster pairs across the fleet - the open risks.

Output parameters:

- `result` (string)

### `list_hosted_clusters` (~97 tokens)

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.

Input parameters:

- `namespace` (string)

Output parameters:

- `result` (string)

### `get_hosted_cluster` (~61 tokens)

Detailed HostedCluster: version, conditions, and its NodePools.

Args:
    name: HostedCluster name.
    namespace: the namespace the HostedCluster lives in (its hosting namespace).

Input parameters:

- `name` (string, required)
- `namespace` (string, required)

Output parameters:

- `result` (string)

### `list_node_pools` (~69 tokens)

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.

Input parameters:

- `cluster` (string)
- `namespace` (string)

Output parameters:

- `result` (string)

### `list_resources` (~132 tokens)

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.

Input parameters:

- `namespace` (string)
- `resource` (string, required)

Output parameters:

- `result` (string)

### `get_resource` (~107 tokens)

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.

Input parameters:

- `name` (string, required)
- `namespace` (string)
- `resource` (string, required)

Output parameters:

- `result` (string)

### `list_pending_proposals` (~24 tokens)

List proposals (ManifestWorks and cluster actions) waiting for human approval.

Output parameters:

- `result` (string)

### `get_audit_trail` (~90 tokens)

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.

Input parameters:

- `last_n` (integer)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ocm-mcp-server-ocm-mcp-server/ghcr-io-ocm-mcp-server-ocm-mcp-server-0-6-0#diagnostics

## Score history

- 2026-09-20: 51
- 2026-09-19: 51
- 2026-09-18: 51
- 2026-09-17: 50
- 2026-09-16: 50
- 2026-09-15: 49
- 2026-09-14: 49
- 2026-09-13: 48
- 2026-09-12: 48
- 2026-09-11: 47
- 2026-09-10: 47
- 2026-09-09: 46
- 2026-09-08: 46
- 2026-09-07: 46
- 2026-09-06: 41
- 2026-09-05: 41
- 2026-09-04: 41
- 2026-09-03: 41
- 2026-09-02: 41
- 2026-09-01: 41
- 2026-08-31: 41
- 2026-08-30: 41
- 2026-08-29: 41

## Common questions

### What is the io.github.ocm-mcp-server/ocm-mcp-server server?

io.github.ocm-mcp-server/ocm-mcp-server is listed in the public MCP registry as io.github.ocm-mcp-server/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/ocm-mcp-server/ocm-mcp-server:0.6.0).

### Is the io.github.ocm-mcp-server/ocm-mcp-server server safe to use?

io.github.ocm-mcp-server/ocm-mcp-server scores 51 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.ocm-mcp-server/ocm-mcp-server server expose?

io.github.ocm-mcp-server/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.ocm-mcp-server/ocm-mcp-server server still maintained?

io.github.ocm-mcp-server/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.ocm-mcp-server/ocm-mcp-server server under?

io.github.ocm-mcp-server/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.

## Links

- Repository: https://github.com/ocm-mcp-server/ocm-mcp-server
- Website: https://github.com/ocm-mcp-server/ocm-mcp-server/wiki
- Changelog RSS feed: https://verifymcp.io/servers/ocm-mcp-server-ocm-mcp-server/ghcr-io-ocm-mcp-server-ocm-mcp-server-0-6-0.xml
- Changelog JSON feed: https://verifymcp.io/servers/ocm-mcp-server-ocm-mcp-server/ghcr-io-ocm-mcp-server-ocm-mcp-server-0-6-0.json
- HTML version of this page: https://verifymcp.io/servers/ocm-mcp-server-ocm-mcp-server/ghcr-io-ocm-mcp-server-ocm-mcp-server-0-6-0