vivac runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 11 Oct 2026.
Provenance tree for coding agents: where you are, why, and what was already decided
What the code does
We read the source, 4 h ago · rules ccca72095570
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.
listing = subprocess.run(
root = os.path.join(base, name)
env = dict(os.environ, VIVAC_HOME=os.path.join(base, ".home"))
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 vivac
same job, measured the same wayYour why agent, the infra agent for your fleet. Your agents work from what you decided, and why.
Memory for coding agents: the decisions, the dead ends, and where the last session stopped.
See what each of your coding agents is working on, and read or advance your todos.
Context integrity for AI agents: evaluate freshness, confidence, provenance, and decision readiness.
Your team's coding agents from any vendor claim work, hand off and prove what shipped, in one room.
Hand a production error to the coding agent you already use — it claims it and writes the fix.
Agents pay for work and prove what happened.
Browser-backed QA with evidence and fix-ready reports for coding agents.
vivac — questions
Answers built from our own checks of this server.