ProofFlow MCP Server

What the code does

We read the source, 5 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        result = subprocess.run(

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.

        result = subprocess.run(

      absPath = path.join(folders[0].uri.fsPath, relPath);

ENV VITE_PROOFFLOW_API_KEY=$VITE_PROOFFLOW_API_KEY

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

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

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

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

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

Optional settings from the registry entry, left out of the block above: PROOFFLOW_BASE_URL (ProofFlow backend URL (default: http://127.0.0.1:8787)), PROOFFLOW_API_KEY (API key for authenticated access to the ProofFlow backend).