Regressguard runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 3 Oct 2026.
Deterministic API regression checks for AI agents: snapshot a baseline, catch broken contracts.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
archivePath := filepath.Join(dir, filename)
select {
case <-rp.done:
return
case <-ticker.C:
rp.frame++
rp.render()
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Regressguard
same job, measured the same wayA structural review layer for Python — baseline-aware, deterministic, built for CI and AI agents
Deterministic, read-only audits of repo readiness for AI coding agents and of agent context files.
Deterministic release gate for AI-written code and coding agents.
Deterministic code map for AI coding agents: a tree-sitter call graph with exact file:line over MCP.
Deterministic code maps for AI agents: 7 tree-sitter tools for TS/JS/Py — map, find, function_body
Deterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.
Deterministic repository oracle for AI agents: inventory, dependency graph, frontend-backend join.
Deterministic navigation maps over code + markdown + Prisma for AI agents: 13 MCP tools
Regressguard — questions
Answers built from our own checks of this server.