Judges Panel MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

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.

    /(?:exec|spawn|system|popen|shell_exec)\s*\(\s*["'`](?:cmd |powershell |bash |sh |\/bin\/|\.exe|rm -rf|del \/|copy |xcopy|chmod|chown)/gi;

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.

  return eval("`" + template + "`");

    return eval(expression)

    const log = execSync(`git log --oneline -${count} --format="%H|%s"`, { encoding: "utf-8", timeout: 10000 });

      - /var/run/docker.sock:/var/run/docker.sock  # Docker socket access

            "and configure your .npmrc to route scoped packages to your private registry.",

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add judges -- npx -y @kevinrabun/judges

{
  "mcpServers": {
    "judges": {
      "args": [
        "-y",
        "@kevinrabun/judges"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.judges]
command = "npx"
args = ["-y", "@kevinrabun/judges"]

{
  "mcpServers": {
    "judges": {
      "args": [
        "-y",
        "@kevinrabun/judges"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "judges": {
      "args": [
        "-y",
        "@kevinrabun/judges"
      ],
      "command": "npx"
    }
  }
}