k8s-cronjob-mcp@2.0.2
CAUTION· install onlyPublisher claims: "A read-only server that enables AI agents to triage Kubernetes CronJobs in a single tool call: whether runs happened and stayed on schedule, whether durations are trending slower or overrunning, which jobs have silently stopped succeeding, and why a given run failed, with evidence and stated basis for each verdict. It also lists active runs and recent failures while enforcing namespace allowlists and no write access." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-13 and scored it 75/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: References a credential file in the home directory; Access to sensitive file paths; References a credential file in the home directory. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
KUBECONFIG absolute path to the kubeconfig (default: ~/.kube/config)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.fix: ["Point it at an existing file, or remove it to use ~/.kube/config"],Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.chmod 600 "$SA_KUBECONFIG"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.what: "No kubeconfig found (KUBECONFIG not set, ~/.kube/config missing)",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.what: "No kubeconfig found (KUBECONFIG not set, ~/.kube/config missing)",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.KUBECONFIG absolute path to the kubeconfig (default: ~/.kube/config)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.fix: ["Point it at an existing file, or remove it to use ~/.kube/config"],Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."default": "${HOME}/.kube/config"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(`Created ${output}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.const s = loadSetup({ KUBECONFIG: "~/.kube/config" });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const s = loadSetup({ KUBECONFIG: "~/.kube/config" });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.code = `Claude Code: claude mcp add k8s-cronjobs -e ${variable}=${value ?? "<value>"} -- npx -y k8s-cronjob-mcp`;Fix: Pin versions and sources; vendor anything fetched at install time.fix: ["Run check_setup (or npx k8s-cronjob-mcp --check) to find the cause"],Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim mshahzadiftikhar: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.