# io.github.CloudCorpRecords/clusterport (npm · @reneturcios/clusterport)

Core kubectl operations: get, describe, logs, apply, scale, patch, rollout and explain.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/clusterport`: 65/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-clusterport/reneturcios-clusterport.md), [page](https://verifymcp.io/servers/cloudcorprecords-clusterport/reneturcios-clusterport)
- oci · `ghcr.io/cloudcorprecords/clusterport`: 41/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-clusterport/ghcr-io-cloudcorprecords-clusterport.md), [page](https://verifymcp.io/servers/cloudcorprecords-clusterport/ghcr-io-cloudcorprecords-clusterport)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/clusterport`
- Version: `0.1.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-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1023 tokens (~85/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kubectl_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/clusterport MCP server?

io.github.CloudCorpRecords/clusterport runs locally as an npm package, launched with npx -y @reneturcios/clusterport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-clusterport -- npx -y @reneturcios/clusterport
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-clusterport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/clusterport"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-clusterport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/clusterport"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-clusterport -- npx -y @reneturcios/clusterport
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-clusterport": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/clusterport"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-clusterport --command npx --arg -y --arg @reneturcios/clusterport
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-clusterport:
    command: "npx"
    args: ["-y", "@reneturcios/clusterport"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-clusterport": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/clusterport"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-clusterport -t stdio -c npx -a -y @reneturcios/clusterport
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-clusterport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/clusterport"
      ]
    }
  }
}
```

## 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-11-04 (score 65, +1)

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

### 2026-11-02 (score 64, +1)

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

### 2026-11-01 (score 63)

First indexed and scored.

## MCP tools (12)

### `kubectl_get` (~117 tokens)

Get Kubernetes resources with kubectl get, as JSON by default.

Input parameters:

- `name` (string): Name of the specific resource to get; when omitted, all resources of the type are listed.
- `namespace` (string): Namespace of the resource to get; when omitted, the current-context default namespace is used.
- `output_format` (string): Output format for kubectl get, such as json or yaml; defaults to json.
- `resource_type` (string, required): Kubernetes resource type to get, such as pods, deployments, or services.

### `kubectl_describe` (~78 tokens)

Describe one Kubernetes resource with kubectl describe.

Input parameters:

- `name` (string, required): Name of the resource to describe.
- `namespace` (string): Namespace of the resource to describe; when omitted, the current-context default namespace is used.
- `resource_type` (string, required): Kubernetes resource type to describe, such as pod, deployment, or service.

### `kubectl_logs` (~79 tokens)

Fetch logs from a Kubernetes pod with kubectl logs.

Input parameters:

- `container` (string): Container name within the pod to fetch logs from, for pods with multiple containers.
- `name` (string, required): Name of the pod to fetch logs from.
- `namespace` (string): Namespace of the pod; when omitted, the current-context default namespace is used.

### `kubectl_apply` (~88 tokens)

Apply a manifest with kubectl apply, sent over stdin.

Input parameters:

- `dry_run` (boolean): When true, run as a client-side dry run without persisting any changes.
- `manifest` (string, required): Kubernetes manifest content to apply, sent to kubectl apply over stdin.
- `namespace` (string): Namespace to apply the manifest into; when omitted, the manifest or default namespace is used.

### `kubectl_create` (~102 tokens)

Create a resource from a generated manifest spec, sent over stdin.

Input parameters:

- `image` (string): Container image to use in the generated manifest; defaults to the resource name when omitted.
- `name` (string, required): Name for the resource to create.
- `namespace` (string): Namespace to create the resource in; when omitted, no namespace is set in the generated manifest.
- `resource_type` (string, required): Kubernetes resource type to create, such as deployment or pod.

### `kubectl_delete` (~77 tokens)

Delete one Kubernetes resource with kubectl delete.

Input parameters:

- `name` (string, required): Name of the resource to delete.
- `namespace` (string): Namespace of the resource to delete; when omitted, the current-context default namespace is used.
- `resource_type` (string, required): Kubernetes resource type to delete, such as pod, deployment, or service.

### `kubectl_scale` (~89 tokens)

Scale a workload with kubectl scale.

Input parameters:

- `name` (string, required): Name of the workload to scale.
- `namespace` (string): Namespace of the workload to scale; when omitted, the current-context default namespace is used.
- `replicas` (number, required): Number of replicas to scale the workload to.
- `resource_type` (string, required): Kubernetes resource type to scale, such as deployment or replicaset.

### `kubectl_patch` (~97 tokens)

Patch one Kubernetes resource with kubectl patch.

Input parameters:

- `name` (string, required): Name of the resource to patch.
- `namespace` (string): Namespace of the resource to patch; when omitted, the current-context default namespace is used.
- `patch` (string, required): Patch content to apply to the resource, passed to kubectl patch with -p.
- `resource_type` (string, required): Kubernetes resource type to patch, such as deployment or service.

### `kubectl_rollout` (~111 tokens)

Run a kubectl rollout action (status, history, restart, undo, pause, resume).

Input parameters:

- `action` (string, required): Rollout action to run: status, history, restart, undo, pause, or resume.
- `name` (string, required): Name of the resource to run the rollout action on.
- `namespace` (string): Namespace of the resource; when omitted, the current-context default namespace is used.
- `resource_type` (string, required): Kubernetes resource type for the rollout, such as deployment.

### `kubectl_context` (~62 tokens)

Read or switch the kubectl context (current, list, use).

Input parameters:

- `name` (string): Name of the context to switch to; required when the operation is use.
- `operation` (string, required): Context operation to perform: current, list, or use.

### `explain_resource` (~71 tokens)

Explain a Kubernetes resource schema with kubectl explain.

Input parameters:

- `api_version` (string): API version to explain the resource against, passed as --api-version; when omitted, the default version is used.
- `resource` (string, required): Kubernetes resource or field path to explain, such as pod or pod.spec.containers.

### `list_api_resources` (~52 tokens)

List the API resources the cluster serves, optionally filtered by kind.

Input parameters:

- `kind` (string): Kind to filter the API resource list by, matched case-insensitively; when omitted, all resources are listed.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-clusterport/reneturcios-clusterport#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63

## Common questions

### What is the io.github.CloudCorpRecords/clusterport MCP server?

io.github.CloudCorpRecords/clusterport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/clusterport. Core kubectl operations: get, describe, logs, apply, scale, patch, rollout and explain. This page covers its npm package (@reneturcios/clusterport).

### Is the io.github.CloudCorpRecords/clusterport MCP server safe to use?

io.github.CloudCorpRecords/clusterport scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 io.github.CloudCorpRecords/clusterport MCP server expose?

io.github.CloudCorpRecords/clusterport exposes 12 tools: kubectl_get, kubectl_describe, kubectl_logs, kubectl_apply, kubectl_create, and 7 more. Their descriptions and schemas cost roughly 1,023 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/clusterport MCP server still maintained?

io.github.CloudCorpRecords/clusterport is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.CloudCorpRecords/clusterport MCP server under?

io.github.CloudCorpRecords/clusterport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/clusterport
- Socket report: https://socket.dev/npm/package/@reneturcios/clusterport
- Repository: https://github.com/CloudCorpRecords/clusterport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-clusterport/reneturcios-clusterport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-clusterport/reneturcios-clusterport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-clusterport/reneturcios-clusterport