Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/smana/cloud-native-ref/flux-operator-mcp)<a href="https://agentmods.dev/mcp/smana/cloud-native-ref/flux-operator-mcp"><img src="https://agentmods.dev/badge/mcp/smana/cloud-native-ref/flux-operator-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade C, and why
flux-operator-mcp scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
"KUBECONFIG": "/home/smana/.kube/config" What it actually says
{
"flux-operator-mcp": {
"command": "/usr/local/bin/flux-operator-mcp",
"args": [
"serve"
],
"env": {
"KUBECONFIG": "/home/smana/.kube/config"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 11 lines scan C 4c1886f75a19
flux-operator-mcp is an MCP server published in the GitHub repository Smana/cloud-native-ref (100 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
vmware-vks
MCP Skill + CLI for managing vSphere with Tanzu (VKS) — Supervisor, Namespaces, and TanzuKubernetesCluster lifecycle. Runs locally from the vmware-vks Python package.
mcp-kubernetes
Kubernetes monitoring & ops for AI agents — safe-by-default access modes and guards. Runs locally from the @dockndevai/mcp-kubernetes npm package. Needs 2 environment variables to run.
talos-mcp-server
MCP server for Talos Linux — resources, services, logs, health, config, lifecycle via gRPC. Runs locally from the talos-mcp npm package. Needs 13 environment variables to run.
devops-mcp
Unified MCP server for Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki. Runs locally from the @notharshhaa/devops-mcp npm package. Needs 9 environment variables to run.
janus-mcp
Secure Kubernetes MCP server: redacted diagnostics and human-approved writes, credentials never leave the process. Runs locally from the janus-mcp-server Python package.
WhiteCapData-Dev
WhiteCapData-Dev — an MCP server to operate a k3s / Kubernetes cluster (health, logs, and guarded restart/scale/delete) straight from your AI agent. Runs locally from the whitecapdata-dev Python package. Needs 4 environment variables to run.