Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.apatilgtn/k8scortex-mcp

OCI · GHCR.IO/APATILGTN/K8SCORTEX-MCP · 2 COMPONENTS

Kubernetes MCP server: 75 tools for GKE, AKS, EKS, RBAC, audit logging, GitOps, multi-cluster.

+3 this week 42 Trust /100

Last scanned (14 hours ago)

Scores higher than 53% of OCI servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 5719 tokens (~76/item across 75 items; 75 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 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 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "restart_pod" 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 75 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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 27 Oct 26 38

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed oci/ghcr.io/apatilgtn/k8scortex-mcp@1.1.3

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 →

MCP tools · 75 exposed · ~5,719 tokens

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 →

Tool Tokens
list_nodes ~27

Lists cluster nodes.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')

No output schema declared.

No examples provided.

list_persistent_volume_claims ~51

Lists PersistentVolumeClaims in a specific namespace with binding and capacity details.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

list_pod_disruption_budgets ~51

Lists PodDisruptionBudgets in a namespace with budget satisfaction status.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
namespacestringyesNamespace

No output schema declared.

No examples provided.

list_pods ~41

Lists pods in a specific namespace.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

list_statefulsets ~43

Lists StatefulSets in a specific namespace.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

list_storage_classes ~32

Lists StorageClasses and indicates default class.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')

No output schema declared.

No examples provided.

list_vpas ~50

Lists VerticalPodAutoscaler objects in a namespace and their update mode/recommendation state.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
namespacestringyesNamespace

No output schema declared.

No examples provided.

list_warning_events ~43

Filters cluster events for warnings in a namespace.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

remove_taint ~74

Removes a specific taint from a node by key.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action
keystringyesTaint key to remove
nodeNamestringyesName of the node

No output schema declared.

No examples provided.

restart_pod ~85

Deletes a pod to force a restart. Usually managed by a deployment/replicaset.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action without making changes
namespacestringyesThe Kubernetes namespace
podNamestringyesThe name of the pod to restart

No output schema declared.

No examples provided.

resume_cronjob ~77

Resumes a suspended CronJob.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
cronJobNamestringyesThe name of the CronJob to resume
dryRunboolean–If true, simulates the action without making changes
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

resume_flux_resource ~92

Resumes reconciliation of a suspended Flux Kustomization or HelmRelease.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action
namestringyesName of the resource
namespacestringyesNamespace of the resource
resourceTypestringyes'kustomization' or 'helmrelease'

No output schema declared.

No examples provided.

rollout_status ~59

Checks deployment rollout status (complete, in-progress, or stalled).

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
deploymentNamestringyesThe name of the deployment
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

rollout_undo ~76

Rolls a deployment back to the previous ReplicaSet template.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
deploymentNamestringyesThe name of the deployment
dryRunboolean–If true, simulates the action without making changes
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

scale_deployment ~83

Scales replicas for a deployment.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
deploymentNamestringyesThe name of the deployment
dryRunboolean–If true, simulates the action without making changes
namespacestringyesThe Kubernetes namespace
replicasnumberyesThe new replica count

No output schema declared.

No examples provided.

set_resource_limits ~168

Sets CPU and Memory requests and limits for a specific container in a Deployment.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
containerNamestringyesThe name of the container
cpuLimitstring–CPU limit (e.g. '500m' or '1')
cpuRequeststring–CPU request (e.g. '100m' or '0.1')
deploymentNamestringyesThe name of the Deployment
dryRunboolean–If true, simulates the action
memoryLimitstring–Memory limit (e.g. '512Mi')
memoryRequeststring–Memory request (e.g. '256Mi')
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

suspend_cronjob ~77

Suspends an active CronJob.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
cronJobNamestringyesThe name of the CronJob to suspend
dryRunboolean–If true, simulates the action without making changes
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

suspend_flux_resource ~95

Suspends reconciliation of a Flux Kustomization or HelmRelease to pause automated deployments.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action
namestringyesName of the resource
namespacestringyesNamespace of the resource
resourceTypestringyes'kustomization' or 'helmrelease'

No output schema declared.

No examples provided.

sync_gitops_app ~140

Forces a sync/reconciliation of an ArgoCD Application, Flux Kustomization, or Flux HelmRelease.

NameTypeReqDescription
appNamestringyesThe name of the application/kustomization/helmrelease
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action
enginestringyesGitOps engine ('argocd' or 'flux')
namespacestringyesThe namespace of the application/kustomization/helmrelease
resourceTypestring–Flux only: 'kustomization' (default) or 'helmrelease'

No output schema declared.

No examples provided.

taint_node ~99

Adds a taint to a node.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action
effectstringyesTaint effect (NoSchedule, PreferNoSchedule, NoExecute)
keystringyesTaint key
nodeNamestringyesName of the node
valuestringyesTaint value

No output schema declared.

No examples provided.

uncordon_node ~64

Marks a node as schedulable.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action
nodeNamestringyesName of the node to uncordon

No output schema declared.

No examples provided.

update_configmap ~97

Updates an existing ConfigMap by patching its data.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
configMapNamestringyesThe name of the ConfigMap to update
dataobjectyesKey-value string pairs to merge into the ConfigMap
dryRunboolean–If true, simulates the action without making changes
namespacestringyesThe Kubernetes namespace

No output schema declared.

No examples provided.

update_ingress ~112

Updates an existing Ingress. Merges new rules or annotations into the existing Ingress.

NameTypeReqDescription
annotationsobject–Annotations to merge
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action without making changes
ingressNamestringyesThe name of the Ingress to update
namespacestringyesThe Kubernetes namespace
rulesarray–Rules to append or replace (advanced usage)

No output schema declared.

No examples provided.

update_secret ~119

Updates an existing Secret: each key in stringData is added or replaced, and keys you do not pass are kept unchanged. Values are never returned.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
dryRunboolean–If true, simulates the action without making changes
namespacestringyesThe Kubernetes namespace
secretNamestringyesThe name of the Secret to update
stringDataobjectyesPlain text key-value pairs to merge into the Secret. Will be encoded automatically.

No output schema declared.

No examples provided.

validate_workload_identity ~62

Validates identity chain from ServiceAccount annotation to pods using that ServiceAccount.

NameTypeReqDescription
clusterstring–Target cluster name (default: 'default')
namespacestringyesServiceAccount namespace
serviceAccountNamestringyesServiceAccount name

No output schema declared.

No examples provided.

Install

How do I install the io.github.apatilgtn/k8scortex-mcp server?

io.github.apatilgtn/k8scortex-mcp runs locally as a container image, launched with docker run --rm -i -e K8SCORTEX_STDIO_ROLES ghcr.io/apatilgtn/k8scortex-mcp:1.1.3 node dist/stdio.js. 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/apatilgtn/k8scortex-mcp

# add to Claude Code
claude mcp add apatilgtn-k8scortex-mcp -- docker run --rm -i -e K8SCORTEX_STDIO_ROLES ghcr.io/apatilgtn/k8scortex-mcp:1.1.3 node dist/stdio.js

This image reads K8SCORTEX_STDIO_ROLES. Set it in your client's env block for this server; docker run -e passes it through to the container.

Common questions

What is the io.github.apatilgtn/k8scortex-mcp server?

io.github.apatilgtn/k8scortex-mcp is listed in the public MCP registry as io.github.apatilgtn/k8scortex-mcp. Kubernetes MCP server: 75 tools for GKE, AKS, EKS, RBAC, audit logging, GitOps, multi-cluster. This page covers its container image (ghcr.io/apatilgtn/k8scortex-mcp).

Is the io.github.apatilgtn/k8scortex-mcp server safe to use?

io.github.apatilgtn/k8scortex-mcp scores 42 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.apatilgtn/k8scortex-mcp server expose?

io.github.apatilgtn/k8scortex-mcp exposes 75 tools: list_pods, get_pod_logs, describe_pod, describe_deployment, list_nodes, and 70 more. Their descriptions and schemas cost roughly 5,719 tokens of context every time the server is loaded.

Is the io.github.apatilgtn/k8scortex-mcp server still maintained?

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

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

What did VerifyMCP test on the io.github.apatilgtn/k8scortex-mcp server?

VerifyMCP ran 12 checks on io.github.apatilgtn/k8scortex-mcp, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.apatilgtn/k8scortex-mcp: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.