Sandboxed test runs for coding agents: compact typed verdicts with failure fingerprints and history
Connect Runs on your machine
claude mcp add verdict-mcp -e VERDICT_PROJECT=<VERDICT_PROJECT> -- uvx verdict-mcp==0.1.0a4
{
"mcpServers": {
"verdict-mcp": {
"command": "uvx",
"args": [
"verdict-mcp==0.1.0a4"
],
"env": {
"VERDICT_PROJECT": "<VERDICT_PROJECT>"
}
}
}
}
{
"mcpServers": {
"verdict-mcp": {
"command": "uvx",
"args": [
"verdict-mcp==0.1.0a4"
],
"env": {
"VERDICT_PROJECT": "<VERDICT_PROJECT>"
}
}
}
}
{
"servers": {
"verdict-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"verdict-mcp==0.1.0a4"
],
"env": {
"VERDICT_PROJECT": "<VERDICT_PROJECT>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
VERDICT_PROJECTOptional | Path to the project to verify (defaults to cwd) |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 25 Aug 2026 |
| Last updated | 25 Aug 2026 |
| Registry name | io.github.Dgotlieb/verdict-mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
