HEIDES runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 8 Oct 2026.
Deterministic code analysis harness giving AI agents senses, memory and judgment for code.
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.
const r = spawnSync(process.execPath, [script], { stdio: "inherit" });
return path.join(__dirname, exe);
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 HEIDES
same job, measured the same wayDeterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.
Deterministic release gate for AI-written code and coding agents.
Deterministic context selection for AI coding agents. Local memory that compounds across sessions.
Deterministic, read-only audits of repo readiness for AI coding agents and of agent context files.
Deterministic repository change-impact analysis for engineers and coding agents.
Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.
Repo-bound memory and self-improving harness for AI coding agents — zero API keys.
Deterministic dev tools for AI agents over MCP: hashing, encoding, formatting, codegen, and more.
HEIDES — questions
Answers built from our own checks of this server.