OpenShift MCP Server
NPM · MCP-SERVER-OPENSHIFT · 2 COMPONENTS
OpenShift/Kubernetes cluster management via the oc CLI for MCP clients
Available components
Last scanned (22 hours ago)
Scores higher than 48% of npm servers
Category Cloud Infrastructure
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.7.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 8 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
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 (MIT).Pass
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3050 tokens (~179/item across 17 items; 14 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "oc_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 0
- CVE-2026-111769 affects this package: high ▼ security
- 17 Oct 26 +2
- Stability: 0.90 → pass security
- 15 Oct 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 4 Nov 2026 · Analysed npm/mcp-server-openshift@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 3 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 8 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
oc_api_resources ~136
List all available API resources in the OpenShift cluster with their details
| Name | Type | Req | Description |
|---|---|---|---|
| apiGroup | string | – | Filter by specific API group (e.g., apps, extensions, networking.k8s.io) |
| categories | boolean | – | Group resources by categories (core, apps, networking, etc.) |
| context | string | – | OpenShift context to use (optional) |
| namespaced | boolean | – | Filter by namespaced resources only |
| output | string | – | Output format for the API resources list |
| verbs | array | – | Filter by supported verbs (e.g., ["get", "list", "create", "delete"]) |
No output schema declared.
No examples provided.
oc_apply ~291
Apply YAML manifests to OpenShift cluster with comprehensive error handling and validation for all scenarios
| Name | Type | Req | Description |
|---|---|---|---|
| cascade | string | – | Deletion cascade strategy |
| context | string | – | OpenShift context to use (optional) |
| dryRun | boolean | – | Validate only, don't apply (client or server) |
| fieldManager | string | – | Field manager name for server-side apply |
| filename | string | – | Path to YAML file to apply |
| force | boolean | – | Force apply, ignore conflicts |
| gracePeriod | number | – | Grace period for resource deletion (seconds) |
| kustomize | boolean | – | Apply kustomization directory |
| manifest | string | – | YAML manifest content to apply |
| namespace | string | – | OpenShift namespace/project |
| overwrite | boolean | – | Overwrite existing resources |
| prune | boolean | – | Prune resources not in current configuration |
| pruneWhitelist | array | – | Resource types to include in pruning |
| recursive | boolean | – | Process directory recursively |
| selector | string | – | Label selector for pruning |
| serverSideApply | boolean | – | Use server-side apply |
| timeout | string | – | Timeout for wait operation (e.g., "60s", "5m") |
| url | string | – | URL to YAML manifest to apply |
| validate | boolean | – | Validate resources before applying |
| wait | boolean | – | Wait for resources to be ready |
No output schema declared.
No examples provided.
oc_create ~189
Create OpenShift resources like projects, deploymentconfigs, routes, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | OpenShift context to use (optional) |
| description | string | – | Description for project |
| displayName | string | – | Display name for project |
| dryRun | boolean | – | Validate only, don't create |
| filename | string | – | Path to YAML file to create resources from |
| hostname | string | – | Hostname for route |
| image | string | – | Container image for deploymentconfig |
| manifest | string | – | YAML manifest to create resources from |
| name | string | – | Name of the resource |
| namespace | string | – | OpenShift namespace/project |
| replicas | number | – | Number of replicas |
| resourceType | string | – | Type of resource to create (project, deploymentconfig, route, service, etc.) |
| service | string | – | Service name for route |
No output schema declared.
No examples provided.
oc_delete ~308
Delete OpenShift resources with comprehensive safety checks, validation, and error handling
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Delete all resources of the specified type |
| allNamespaces | boolean | – | Delete resources across all namespaces |
| cascade | string | – | Deletion cascade strategy |
| confirm | boolean | – | Require explicit confirmation for destructive operations |
| context | string | – | OpenShift context to use (optional) |
| dryRun | boolean | – | Show what would be deleted without actually deleting |
| fieldSelector | string | – | Delete resources matching field selector |
| filename | string | – | Path to YAML file to delete resources from |
| force | boolean | – | Force deletion (bypass finalizers) |
| gracePeriodSeconds | number | – | Grace period for deletion in seconds |
| ignore404 | boolean | – | Ignore 404 errors if resource does not exist |
| labelSelector | string | – | Delete resources matching label selector |
| manifest | string | – | YAML manifest defining resources to delete |
| name | string | – | Name of the resource to delete |
| namespace | string | – | OpenShift namespace/project |
| recursive | boolean | – | Process directory recursively |
| resourceType | string | – | Type of resource to delete (required if not using manifest/filename) |
| timeout | string | – | Timeout for deletion operation (e.g., "60s", "5m") |
| url | string | – | URL to YAML manifest defining resources to delete |
| wait | boolean | – | Wait for deletion to complete |
No output schema declared.
No examples provided.
oc_describe ~114
Describe any OpenShift resource and share the output in various formats including human-readable summary
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | OpenShift context to use (optional) |
| name | string | yes | Name of the resource to describe |
| namespace | string | – | OpenShift namespace/project |
| output | string | – | Output format: text (default oc describe), yaml, json, or human-readable (concise summary) |
| resourceType | string | yes | Type of resource to describe (pod, deployment, service, route, etc.) |
No output schema declared.
No examples provided.
oc_explain ~135
Explain OpenShift/Kubernetes resource schemas, fields, and API documentation
| Name | Type | Req | Description |
|---|---|---|---|
| apiVersion | string | – | Specific API version to explain (e.g., apps/v1, route.openshift.io/v1) |
| context | string | – | OpenShift context to use (optional) |
| field | string | – | Specific field path to explain (e.g., spec.containers, metadata.labels) |
| output | string | – | Output format for the explanation |
| recursive | boolean | – | Show all fields recursively |
| resource | string | yes | Resource type to explain (e.g., pod, deployment, service, route.route.openshift.io) |
No output schema declared.
No examples provided.
oc_expose ~377
Expose an OpenShift resource (service, deployment, etc.) with secure route endpoints supporting SSL/TLS termination
| Name | Type | Req | Description |
|---|---|---|---|
| annotations | array | – | Annotations to apply to the route in KEY=VALUE format |
| caCertificate | string | – | Path to CA certificate file |
| certificate | string | – | Path to TLS certificate file |
| context | string | – | OpenShift context to use (optional) |
| destinationCaCertificate | string | – | Path to destination CA certificate file (for reencrypt) |
| dryRun | boolean | – | Show what would be created without actually creating it |
| hostname | string | – | Custom hostname for the route |
| insecureEdgeTerminationPolicy | string | – | Policy for insecure traffic: None (reject), Allow (allow), Redirect (redirect to secure) |
| key | string | – | Path to TLS private key file |
| labels | array | – | Labels to apply to the route in KEY=VALUE format |
| name | string | yes | Name of the resource to expose |
| namespace | string | – | OpenShift namespace/project |
| path | string | – | Path for the route (e.g., /api) |
| port | string | – | Target port to expose (port name or number) |
| resourceType | string | yes | Resource type to expose (service, deploymentconfig, deployment) |
| routeName | string | – | Name for the route (if not specified, derives from resource name) |
| routeType | string | – | Type of secure route: edge (SSL termination at router), passthrough (SSL passthrough), reencrypt (SSL re-encryption) |
| tlsTermination | string | – | TLS termination type (deprecated, use routeType instead) |
| weight | number | – | Weight for this route (0-256) |
| wildcardPolicy | string | – | Wildcard policy for the route |
No output schema declared.
No examples provided.
oc_get ~153
Get OpenShift resources like pods, deploymentconfigs, routes, projects, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| allNamespaces | boolean | – | List resources across all namespaces |
| context | string | – | OpenShift context to use (optional) |
| fieldSelector | string | – | Filter resources by field selector |
| labelSelector | string | – | Filter resources by label selector (e.g., app=nginx) |
| name | string | – | Name of the resource (optional - if not provided, lists all resources) |
| namespace | string | – | OpenShift namespace/project |
| output | string | – | Output format |
| resourceType | string | yes | Type of resource to get (e.g., pods, deploymentconfigs, routes, projects, services) |
No output schema declared.
No examples provided.
oc_install_operator ~216
Install an Operator on the OpenShift/Kubernetes cluster using OLM, Helm, or direct manifests
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Update channel for the operator (stable, alpha, beta, etc.) |
| context | string | – | OpenShift context to use (optional) |
| createNamespace | boolean | – | Create namespace if it does not exist |
| helmRepo | string | – | Helm repository URL (required if source is helm) |
| installPlanApproval | string | – | Install plan approval strategy for OLM |
| manifestUrl | string | – | URL to operator manifest (required if source is manifest) |
| namespace | string | – | Target namespace for operator installation |
| operatorName | string | yes | Name of the operator to install (e.g., "prometheus-operator", "cert-manager") |
| source | string | – | Installation method: olm (Operator Lifecycle Manager), helm (Helm chart), or manifest (direct YAML) |
| version | string | – | Version of the operator to install (if not specified, installs latest available) |
No output schema declared.
No examples provided.
oc_login ~189
Securely log into an OpenShift cluster using username/password or token authentication
| Name | Type | Req | Description |
|---|---|---|---|
| authMethod | string | yes | Authentication method to use |
| certificateAuthority | string | – | Path to certificate authority file for TLS verification |
| context | string | – | Context name to save the login session (optional) |
| insecureSkipTlsVerify | boolean | – | Skip TLS certificate verification (not recommended for production) |
| namespace | string | – | Default namespace to set after login |
| password | string | – | Password for password authentication (required if authMethod is password) |
| server | string | yes | OpenShift cluster server URL (e.g., https://api.cluster.example.com:6443) |
| timeout | number | – | Login timeout in seconds |
| token | string | – | OpenShift authentication token (required if authMethod is token) |
| username | string | – | Username for password authentication (required if authMethod is password) |
No output schema declared.
No examples provided.
oc_logs ~261
Get logs from OpenShift resources like pods, deployments, builds, etc. with advanced filtering and streaming options
| Name | Type | Req | Description |
|---|---|---|---|
| allContainers | boolean | – | Get logs from all containers in the pod |
| container | string | – | Container name (for pods with multiple containers) |
| context | string | – | OpenShift context to use (optional) |
| follow | boolean | – | Follow logs output (stream live logs) |
| limitBytes | number | – | Maximum bytes to return |
| maxLogRequests | number | – | Maximum number of concurrent log requests when using selectors |
| name | string | yes | Name of the resource |
| namespace | string | – | OpenShift namespace/project |
| previous | boolean | – | Show logs from previous terminated container |
| resourceType | string | – | Type of resource to get logs from |
| selector | string | – | Label selector to filter pods |
| since | string | – | Show logs since relative time (e.g. 5s, 2m, 3h) or absolute time |
| sinceTime | string | – | Show logs since absolute timestamp (RFC3339) |
| tail | number | – | Number of lines to show from end of logs (-1 for all) |
| timestamps | boolean | – | Include timestamps in log output |
No output schema declared.
No examples provided.
oc_new_app ~271
Create a new application from a GitHub repository using S2I build and expose it with an edge-terminated route
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | – | Name for the application (if not specified, derives from repo name) |
| builderImage | string | – | Builder image for S2I build (e.g., "nodejs:18-ubi8", "python:3.9-ubi8") |
| context | string | – | OpenShift context to use (optional) |
| contextDir | string | – | Context directory within the Git repository |
| createNamespace | boolean | – | Create namespace if it does not exist |
| env | array | – | Environment variables in KEY=VALUE format |
| exposeRoute | boolean | – | Create an edge-terminated route to expose the application |
| gitRef | string | – | Git reference (branch, tag, or commit) to build from (default: main/master) |
| gitRepo | string | yes | GitHub repository URL for the source code |
| labels | array | – | Labels in KEY=VALUE format |
| namespace | string | – | Target namespace for the application |
| routeHostname | string | – | Custom hostname for the route (if not specified, uses default) |
| strategy | string | – | Build strategy: source (S2I) or docker |
No output schema declared.
No examples provided.
oc_patch ~233
Patch OpenShift resources with strategic merge, JSON merge, or JSON patch operations
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | OpenShift context to use (optional) |
| dryRun | boolean | – | Perform a dry run without making actual changes |
| fieldManager | string | – | Field manager name for server-side apply tracking |
| force | boolean | – | Force the patch operation, ignoring conflicts |
| name | string | yes | Name of the resource to patch |
| namespace | string | – | Namespace/project for the resource (not required for cluster-scoped resources) |
| patch | string | yes | Patch content as JSON string or YAML. For strategic merge patch (default), provide the fields to update. For JSON patch, use RFC 6902 format. |
| patchType | string | – | Type of patch operation |
| recordHistory | boolean | – | Record the patch operation in the resource annotation for rollback purposes |
| resourceType | string | yes | Type of resource to patch (pod, deployment, service, route, configmap, secret, etc.) |
| subresource | string | – | Subresource to patch (e.g., status, scale) |
No output schema declared.
No examples provided.
oc_scale ~109
Scale the number of pods in a deployment, deploymentconfig, replicaset, or statefulset to the specified number of replicas
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | OpenShift context to use (optional) |
| name | string | yes | Name of the resource to scale |
| namespace | string | – | OpenShift namespace/project |
| replicas | number | yes | Number of replicas to scale to |
| resourceType | string | – | Resource type to scale (deployment, deploymentconfig, replicaset, statefulset) |
No output schema declared.
No examples provided.
How do I install the OpenShift MCP Server server?
OpenShift MCP Server runs locally as an npm package, launched with npx -y mcp-server-openshift. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-server-openshift
claude mcp add sanjaypsachdev-mcp-server-openshift -- npx -y mcp-server-openshift
What is the OpenShift MCP Server server?
OpenShift MCP Server is listed in the public MCP registry as io.github.sanjaypsachdev/mcp-server-openshift. OpenShift/Kubernetes cluster management via the oc CLI for MCP clients. This page covers its npm package (mcp-server-openshift).
Is the OpenShift MCP Server server safe to use?
OpenShift MCP Server scores 74 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. 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 OpenShift MCP Server server expose?
OpenShift MCP Server exposes 14 tools: oc_get, oc_create, oc_install_operator, oc_new_app, oc_scale, and 9 more. Their descriptions and schemas cost roughly 2,982 tokens of context every time the server is loaded.
Is the OpenShift MCP Server server still maintained?
OpenShift MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 November 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 OpenShift MCP Server server under?
OpenShift MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.