Whiskers runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 1 Nov 2026.
Governed Docker and Kubernetes operations for AI agents: scoped keys, guardrails, human approvals.
What the code does
We read the source, 22 h ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
{ "host.exec", """{"serverId":"local","command":"rm -rf /opt/dockerproxy"}""" }, // a host's tunnel keys
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
using var p = Process.Start(new ProcessStartInfo(file, args)
- /var/run/docker.sock:/var/run/docker.sock
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Whiskers and you get told the day something new turns up.
Alternatives to Whiskers
same job, measured the same wayKubernetes MCP server with RBAC-style, context-scoped guardrails for AI agents.
Governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals.
Guardrailed fleet ops for AI agents: multi-cluster Kubernetes via OCM with policy, approval, audit.
Guardrailed fleet ops for AI agents: multi-cluster Kubernetes via OCM with policy, approval, audit.
Secure Kubernetes MCP server: scoped, redacted diagnostics and human-approved writes
Kubernetes monitoring & ops for AI agents — safe-by-default access modes and guards.
Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients.
Kubernetes MCP server for diagnosis, resource management, GitOps, and RBAC-enforced operations.
Whiskers — questions
Answers built from our own checks of this server.