Developer · Local MCP server
Verirun
Execution-grounded verification for AI coding agents on Windows: evidence, not agent claims.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.baopeak/verirun- Version
- 0.2.1-dev
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-14
- Updated
- 2026-09-14
- Publisher
- baopeak (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/baopeak) · how
- Repository
- github.com/baopeak/verirun
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | verirun | 0.2.1-dev | stdio |
How to connect Verirun
Verirun runs locally from a Node.js package published to the npm registry: verirun version 0.2.1-dev. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y verirun@0.2.1-dev. It reads these environment variables: VERIRUN_ALLOW_INPUT_INJECTION, VERIRUN_ALLOW_ENDPOINT_REPIN and VERIRUN_DATA_DIR; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"verirun": {
"command": "npx",
"args": [
"-y",
"verirun@0.2.1-dev"
],
"env": {
"VERIRUN_ALLOW_INPUT_INJECTION": "<value>",
"VERIRUN_ALLOW_ENDPOINT_REPIN": "<value>",
"VERIRUN_DATA_DIR": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Verified Repo MemoryStale-proof repository memory with citations + just-in-time verification + TTL (repo-scoped). | Local · stdio |
| Verify APIEvidence-backed verification for citations, packages, repos, cases, filings, drugs, x402 sellers. | Local · stdio |
| Verify SCITT receipts from Forestrie transparency logs, offlineVerify a SCITT receipt under a trust root you hold - offline, no backend, no key, no network. | Local · stdio |
| verimcpTransparent MCP proxy that independently re-verifies tool-call claims before the Host trusts them. | Local · stdio |
| VerisBehavioral verification intelligence for AI coding agents. 17 MCP tools. Local-first. MIT. | Local · stdio |
| VeriTeknikManage VeriTeknik servers, DNS, backups and support tickets from your AI assistant. | Remote · HTTPLive check: sign-in required |
| Verlon AI MCPInspect and manage Verlon AI gates, logs, recommendations, and experiments from any MCP client. | Local · stdio |
| VersionlyMonitor third-party API changes in GitHub repos, map breaks to files, open reviewable auto-fix PRs. | Remote · HTTPLive check: sign-in required |