mcpField
V
verirun

verirun

Local
github.com/baopeakDeveloper Tools
Repository

About verirun

Execution-grounded verification for AI coding agents on Windows: evidence, not agent claims

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "baopeak-verirun": {
      "command": "npx",
      "args": [
        "-y",
        "verirun"
      ],
      "env": {
        "VERIRUN_ALLOW_INPUT_INJECTION": "<VERIRUN_ALLOW_INPUT_INJECTION>",
        "VERIRUN_ALLOW_ENDPOINT_REPIN": "<VERIRUN_ALLOW_ENDPOINT_REPIN>",
        "VERIRUN_DATA_DIR": "<VERIRUN_DATA_DIR>"
      }
    }
  }
}
Run commandnpx -y verirun
Environment variables to set
VERIRUN_ALLOW_INPUT_INJECTIONSet to 1 to allow Tier C (OS-wide send-input/click). User-side only; off by default.
VERIRUN_ALLOW_ENDPOINT_REPINSet to 1 to let a declared endpoint keep working after its DNS answer moves to a different address (each move is recorded). Off by default: a moved endpoint is refused.
VERIRUN_DATA_DIROverride the evidence-record directory (default %LOCALAPPDATA%\Verirun\runs).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmverirun0.2.1-dev

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.