Agent Residue Evidence runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 28 Aug 2026.
Report local task-scoped test and build residue without cleaning resources.
What the code does
We read the source, 12 h ago · rules 3dff92dd89df
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.
return atomicWriteJSON(filepath.Join(directory, name), envelope)
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 Agent Residue Evidence
same job, measured the same wayTask management for teams building with AI agents. Agents claim tasks and report progress.
FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.
Browser-backed QA with evidence and fix-ready reports for coding agents.
Local proof facts for AI coding clients: intent, tests, Graph Ops, and review evidence.
Repo analysis for coding agents with ranked files, dependency maps, and task-scoped context.
Source-linked building-permit search across 34 US states and DC, with county-level coverage.
AI agent project management — task boards, progress tracking, and cost reporting.
Advisory AOS agent health scan before deployment (manifest, services, immune loop, evidence).
Agent Residue Evidence — questions
Answers built from our own checks of this server.