Vinv — Claude Code MCP server: runtime testing and verification
Vinv links runtime traces to source code and verifies agent edits by re-running them. Gives your agent proof of how the code actually behaves when it runs.
Apache-2.0 ★ 48 updated 2026-10-20
claude mcp add --env VINV_WORKSPACE=<VINV_WORKSPACE> --transport stdio vinv -- npx -y vinv-mcpWhat Vinv does
Vinv provides 16 tools: semantic search across the codebase, dead code detection, fault localization from execution traces, runtime value extraction, and coverage data. It builds workspace context in the .vinv/ folder — code graph, traces, and metrics tied to the functions that handled each request. Every agent reads the same .vinv/ store.
First build requires uv and Rust, takes about three minutes, and downloads a roughly 100 MB embedding model. First trace lands about a minute after the build finishes; everything after that runs in seconds. Vinv runs entirely locally with no telemetry.
What it helps with
- verify an agent's fix by re-running the code
- find a bug from a service execution trace
- link runtime behavior to the exact source function
- track coverage and variable values during execution
- localize an error in a running application
Example prompts for the agent
- Find dead code in this project
- Show runtime values for the
process_requestfunction from the last run - Which functions were called during this request?
How to install Vinv
Platform CLI
claude mcp add --env VINV_WORKSPACE=<VINV_WORKSPACE> --transport stdio vinv -- npx -y vinv-mcpReplace <…> with your own values
Platform CLI
codex mcp add vinv --env VINV_WORKSPACE=<VINV_WORKSPACE> -- npx -y vinv-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"vinv": {
"command": "npx",
"args": [
"-y",
"vinv-mcp"
],
"env": {
"VINV_WORKSPACE": "<VINV_WORKSPACE>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"vinv": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vinv-mcp"
],
"env": {
"VINV_WORKSPACE": "<VINV_WORKSPACE>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e VINV_WORKSPACE=<VINV_WORKSPACE> vinv npx -y vinv-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Vinv
How do I install Vinv in Claude Code?
Run claude mcp add vinv -- npx -y vinv-mcp in your terminal. To specify a workspace directory, add --env VINV_WORKSPACE=<path> before vinv.
What does Vinv do?
Vinv collects execution traces, links them to source code, and gives your agent tools to find bugs, verify edits, and analyze coverage. The agent gets proof of how the code actually behaves.
What do I need to run Vinv for the first time?
You need uv and Rust installed. First build takes about three minutes and downloads a roughly 100 MB embedding model. After that, everything runs in seconds.