
Verirun
io.github.baopeakPublished by GitHub account baopeakv0.2.1-devUpdated Oct 24, 2026
Execution-grounded verification for AI coding agents on Windows: evidence, not agent claims.
Overview
Windows-only local MCP server that gives AI coding agents execution-grounded verification, recording evidence instead of relying on agent claims.
- What you can do
- Verifies coding-agent work by actually running it on Windows and capturing evidence records.
- Keeps an evidence-record directory for runs, which can be relocated.
- Guards declared endpoints against DNS changes, refusing a moved endpoint unless explicitly allowed.
- Optionally permits OS-wide send-input and click actions (Tier C) when enabled by the user.
- When to use it
- Useful when you want an AI coding agent's claims about its changes checked by real execution on a Windows machine, and you want a recorded trail of that verification rather than the agent's own word.
- Requirements
- Runs as a local stdio process via npx (Node.js). Windows desktop only; no web execution. Optional environment variables: VERIRUN_DATA_DIR to change the evidence-record directory, VERIRUN_ALLOW_ENDPOINT_REPIN to allow endpoints whose DNS answer moves, and VERIRUN_ALLOW_INPUT_INJECTION to enable OS-wide input and click actions. No authentication declared.
Installation
In SourceWeft
- Open Verirun in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.2.1-devLatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.