tensilestream/buildanchor

Local-first Build Truth & verification layer for AI coding agents. Stops hallucinations, cuts token costs by 90%, and fixes monorepo test failures for Claude, Cursor, Aider, & Copilot.

About buildanchor

BuildAnchor tells you the command that builds and tests this repository — and whether it actually runs. Open source, local-first, offline, no LLM calls. By Tensilestream.

Every tool of this kind can read a manifest and report what it found. None of them can tell you whether the command they found works — and a plausible, wrong command is expensive: an agent pays for the tool call, a screen of collection errors in its context, and a repair turn. So BuildAnchor executes a cheap discovery probe and reports how far the command is actually proven:

Status Meaning --- --- declared Found in a manifest. A candidate — this is where other tools stop. resolvable Its entrypoint exists on disk or PATH. Nothing executed. collects A discovery-only probe exited 0 in the right directory. Seconds. passes The full command exited 0.

Commands always come with the directory they run in, because pytest lib-a from the repository root is not the same thing as pytest inside lib-a, and in a repository with more than one project only the second one works.

It knows the difference between a monorepo, a single project, and a root project with an SDK beside it — and only gives you scoping advice when there is a scoping decision to make.

On twelve real, unmodified public repositories — cloned at benchmark time, none of them ours:

Gets the project's own test command --- --- Guessing from the manifest (pytest, npm test, go test ./...) 7 / 12 — 58% BuildAnchor 12 / 12 — 100%

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/tensilestream--buildanchor.html)

Related MCP servers