Browse / MCP servers
aashishmahajan/kube-noob
public agent for training everything kubernetes, helm, openshift rosa and stackrox
- MCP
Works.Tested on 2026-10-27. From the README alone, on Linux with Haiku and Linux with Luna.
What we checked
Does it run from the README?Yes. Running in 3:44 on a clean Linux box.The run
Tested Oct 27, 2026, rev 42e1f4f.
Does it do what the README says?3 of 3 claims held up.Evidence
“Answers cite local knowledge as [kn:<doc>#<n>] chunk ids”
Expected search result cites kn:k8s-probes#0. Got kn:k8s-probes#0.
“Audit finds issues in a Deployment with rules such as KN-S013”
Expected report lists KN-S013 hardcoded DB_PASSWORD finding. Got KN-S013.
“Debug diagnoses a CrashLoop from pasted events”
Expected diagnosis id DBG-CRASHLOOP. Got DBG-CRASHLOOP.
Which checks were skipped?1 check skipped.Reasons
Skipped checks count as neither passes nor failures.
Cycles: 1 skipped
- Watch namespaces on a schedule-like loop (polls every interval; --once runs one pass): Missing prerequisite: no cluster. Observed: 'error: No cluster backend available: not in a pod and neither oc nor kubectl is on PATH.' rc=4. No cycle replayed.
Which setups did we try?Works with Haiku, Luna.Setups
Linux / Haiku: works, Oct 27, rev 42e1f4f. Linux / Luna: works, Oct 27, rev 42e1f4f.
Needs keys, a login or a browser?No.Details
None seen
Is it safe to run?No unexpected network or file activity found in these checksWhat we saw
No problems traced to this repository code in these checks; a short run cannot prove safety. 2 listed items (named-host connections, static matches, dependency advisories) are below and do not change this verdict. 16 static matches retained as context.
Gitleaks found a possible hardcoded secret; value withheld. scripts/e2e_mcp_offline.py
Reviewed as expected for a test run: attempted writes that failed, so nothing was written.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Maintained · 56 commits in 90 days · 0 merged PRs in 90 days · 1 open issues · 0 open PRsActivity
actively maintained: last commit 0 days ago; 56 commits and 0 merged PRs in 90 days; 1 open issues, 0 open PRs; latest release 2026-10-27
Can I show this on my README?Copy the badge.Badge
The run
Oct 27 · rev 42e1f4fIndependent test, not endorsed by the project.