io.github.CloudCorpRecords/clusterport
NPM · @RENETURCIOS/CLUSTERPORT · 2 COMPONENTS
Core kubectl operations: get, describe, logs, apply, scale, patch, rollout and explain.
Available components
Last scanned (20 hours ago)
Scores higher than 33% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1023 tokens (~85/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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; "kubectl_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 12 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
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 63
First indexed and scored.
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/@reneturcios/clusterport@0.1.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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
explain_resource ~71
Explain a Kubernetes resource schema with kubectl explain.
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | – | API version to explain the resource against, passed as --api-version; when omitted, the default version is used. |
| resource | string | yes | Kubernetes resource or field path to explain, such as pod or pod.spec.containers. |
No output schema declared.
No examples provided.
kubectl_apply ~88
Apply a manifest with kubectl apply, sent over stdin.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | When true, run as a client-side dry run without persisting any changes. |
| manifest | string | yes | 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. |
No output schema declared.
No examples provided.
kubectl_context ~62
Read or switch the kubectl context (current, list, use).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Name of the context to switch to; required when the operation is use. |
| operation | string | yes | Context operation to perform: current, list, or use. |
No output schema declared.
No examples provided.
kubectl_create ~102
Create a resource from a generated manifest spec, sent over stdin.
| Name | Type | Req | Description |
|---|---|---|---|
| image | string | – | Container image to use in the generated manifest; defaults to the resource name when omitted. |
| name | string | yes | 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 | yes | Kubernetes resource type to create, such as deployment or pod. |
No output schema declared.
No examples provided.
kubectl_delete ~77
Delete one Kubernetes resource with kubectl delete.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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 | yes | Kubernetes resource type to delete, such as pod, deployment, or service. |
No output schema declared.
No examples provided.
kubectl_describe ~78
Describe one Kubernetes resource with kubectl describe.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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 | yes | Kubernetes resource type to describe, such as pod, deployment, or service. |
No output schema declared.
No examples provided.
kubectl_get ~117
Get Kubernetes resources with kubectl get, as JSON by default.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Kubernetes resource type to get, such as pods, deployments, or services. |
No output schema declared.
No examples provided.
kubectl_logs ~79
Fetch logs from a Kubernetes pod with kubectl logs.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | – | Container name within the pod to fetch logs from, for pods with multiple containers. |
| name | string | yes | Name of the pod to fetch logs from. |
| namespace | string | – | Namespace of the pod; when omitted, the current-context default namespace is used. |
No output schema declared.
No examples provided.
kubectl_patch ~97
Patch one Kubernetes resource with kubectl patch.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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 | yes | Patch content to apply to the resource, passed to kubectl patch with -p. |
| resource_type | string | yes | Kubernetes resource type to patch, such as deployment or service. |
No output schema declared.
No examples provided.
kubectl_rollout ~111
Run a kubectl rollout action (status, history, restart, undo, pause, resume).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Rollout action to run: status, history, restart, undo, pause, or resume. |
| name | string | yes | 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 | yes | Kubernetes resource type for the rollout, such as deployment. |
No output schema declared.
No examples provided.
kubectl_scale ~89
Scale a workload with kubectl scale.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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 | yes | Number of replicas to scale the workload to. |
| resource_type | string | yes | Kubernetes resource type to scale, such as deployment or replicaset. |
No output schema declared.
No examples provided.
list_api_resources ~52
List the API resources the cluster serves, optionally filtered by kind.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Kind to filter the API resource list by, matched case-insensitively; when omitted, all resources are listed. |
No output schema declared.
No examples provided.
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.
npm · @reneturcios/clusterport
claude mcp add cloudcorprecords-clusterport -- npx -y @reneturcios/clusterport
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 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 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 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 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.