zzop runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 25 Oct 2026.
Deterministic repository oracle for AI agents: inventory, dependency graph, frontend-backend join.
What the code does
We read the source, 1 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.
const devPath = path.join(__dirname, '..', '..', '..', 'target', 'release', devBin);
const result = spawnSync(binaryPath, process.argv.slice(2), { stdio: 'inherit' });
document.getElementById('glegend').innerHTML = Object.keys(counts)
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 zzop
same job, measured the same wayDeterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.
Deterministic repository structure mapping for onboarding agents.
Deterministic repository change-impact analysis for engineers and coding agents.
Cross-repository semantic code intelligence for AI coding agents, from a local code graph.
Deterministic release gate for AI-written code and coding agents.
Deterministic, read-only audits of repo readiness for AI coding agents and of agent context files.
AI code impact analysis — dependency graphs, cascade detection, and build gates for AI agents
Deterministic code map for AI coding agents: a tree-sitter call graph with exact file:line over MCP.
zzop — questions
Answers built from our own checks of this server.