Krauncher analyzer MCP Server

What the code does

We read the source, 1 h ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        subprocess.run(["fallocate", "-l", "4G", scratch], check=True)

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 krauncher-mcp -- uvx krauncher-mcp

{
  "mcpServers": {
    "krauncher-mcp": {
      "command": "uvx",
      "args": [
        "krauncher-mcp"
      ]
    }
  }
}

[mcp_servers.krauncher-mcp]
command = "uvx"
args = ["krauncher-mcp"]

{
  "mcpServers": {
    "krauncher-mcp": {
      "command": "uvx",
      "args": [
        "krauncher-mcp"
      ]
    }
  }
}

{
  "servers": {
    "krauncher-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "krauncher-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: KRAUNCHER_API_KEY (Optional Krauncher API key (get one at https://krauncher.com). Without it the server calls the public analyzer keyless, under a per-IP daily quota; with it, your keyed account is used and the quota is skipped).