Agent Residue Evidence MCP server
Report local task-scoped test and build residue without cleaning resources.
0 stars
Reviews
Write oneNobody has reviewed Agent Residue Evidence yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Agent Residue Evidence tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 48 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Agent Residue Evidence compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 40% of 1,299 Productivity servers
Install Agent Residue Evidence in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Agent Residue Evidence repository's README, as published. We do not edit it. Read it on GitHub
Agent Residue Evidence
Agent Residue Evidence (ARE) adds an evidence checkpoint to an Agent's test and build workflow:
observe → Agent reviews evidence → user authorizes cleanup
→ Agent cleans with its own tools → ARE verifiesARE shows task-scoped files, directories, attributed processes, and their listening ports. It never deletes files, stops processes, closes ports, decides that something is safe to delete, scans the full machine, uploads data, uses the network, or collects telemetry.
Visit the project site, run the reproducible task-residue demo, or download the latest verified release.
Standard task
Before the first test or build, the Agent calls begintaskobservation with the exact workspace and any task-owned temporary roots. Events are optional; safe generic events or empty heartbeats can be sent with appendtaskevents. Before its final answer, the Agent calls endtaskobservation, explains the candidates, and asks the user what to do. Only after explicit authorization does the Agent clean with its normal tools. It then calls verifytaskresidue to recheck the same stable candidates.
NOCANDIDATESOBSERVED means only that no candidate appeared inside the declared observation scope. It is not a host-wide cleanliness claim.
Completed task without a baseline
inspectcompletedtask accepts explicit roots and a bounded time window. The result is always PARTIALEVIDENCE; it can use Event, receipt, inferred, or unattributed evidence, but never claims BASELINEOBSERVED. Use getresiduereport to read a saved report without observing again.
Every observation is isolated by an opaque owner capability. Task IDs, report IDs, observation IDs, and candidate IDs are display references only and never authorize access. State is encrypted at rest with opaque filenames; exact paths are revealed only through an authorized candidate-resolution call. Short-lived executor capabilities can append only explicitly allowed event types and root aliases and cannot read, end, verify, or resolve a task.
The MCP surface contains exactly eight tools:
- begintaskobservation
- appendtaskevents
- endtaskobservation
- inspectcompletedtask
- getresiduereport
- verifytaskresidue
- delegatetaskexecutor
- resolveresiduecandidate
There is deliberately no cleanup, delete, execute, terminate, or close tool.
Local-first packaging
One release contains a native CLI/stdio MCP server, thin Agent Plugin, MCPB, checksums, provenance, and SPDX SBOM. See Quickstart and Install. Runtime operation is fully local and offline. Reports default to seven-day retention and a 100 MB total cap; retained reports and active baselines are protected. Uninstall never silently deletes reports.
The current release is published in the official MCP Registry as io.github.fantasyce/agent-residue-evidence.
Native acceptance covers macOS 14+ arm64, Linux amd64, and Windows 11 amd64 through mandatory native CI jobs. Cross-compilation alone is not reported as native acceptance.
Agent Reliability Toolkit
ARE is one independent part of a small, local-first reliability toolkit:
- Agent Recall Trail keeps private Agent memory separate from reviewed shared knowledge.
- Agent Runtime Proof verifies that a live Agent or MCP runtime matches the artifact you approved.
- Agent Residue Evidence records task-scoped files, processes, and listening ports left by tests and builds.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Agent Residue Evidence: common questions
- Is Agent Residue Evidence MCP server safe?
- Mostly: it is graded B (75/100). Read the Agent Residue Evidence safety report
- Does Agent Residue Evidence need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Agent Residue Evidence maintained?
- The last commit was 52 days ago (2026-09-13). The latest release is v0.3.0.
- What can I use instead of Agent Residue Evidence?
- Servers from other publishers that do the same job: boxpdf MCP server, Orbit MCP server and Hive Vault MCP server.
Alternatives to Agent Residue Evidence
Same job from other publishers: the closest match first, then the best rated.
- boxpdfResource-only MCP server with docs and templates for the boxpdf TypeScript PDF layout library.not reviewedGrowingA
OrbitTask management for people and AI agents, with scoped OAuth access to issues, projects, and docs.not reviewedGrowingA- Hive VaultOn-demand Obsidian vault access for AI coding assistants — 17 tools, 5 resources, 4 prompts.not reviewedGrowingB