Purr Verify MCP

Why it exists

Agent-driven repository work still needs the same evidence as human development: a clean install, type checking, tests, lint, and a production build.

The verification service keeps that runtime work separate from the tools that edit GitHub repositories.

Current scope

The server clones a requested repository reference into an isolated workspace, runs allowlisted commands, and returns structured job results.

• Asynchronous verification jobs
• Explicit command and job timeout policies
• Allowlisted install, test, typecheck, lint, and build commands
• Structured command output and terminal job status
• Separate read-only verification role

How it is used

A repository change is committed first. The verification job then checks that exact branch or commit. The result can be attached to a pull request before merge and repeated on the default branch afterward.

Status

The project is active and used for verification across the current HeyCatLabs repository workflows. Work continues around reproducibility, job retention, and clearer failure evidence.