Evidence Diff
Explain coarse Git and test-build evidence changes without source diff contents. Tools include...
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: only reads or looks up information.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y evidence-diff-mcp
MCP client config
{
"mcpServers": {
"evidence-diff": {
"command": "npx",
"args": [
"-y",
"evidence-diff-mcp"
]
}
}
}evidence-diff-mcp
Evidence Diff is a local MCP tool for explaining coarse changes in a Git project’s test and build evidence. It can tell an agent that a worktree changed, that uncommitted evidence exists, or that test-like artifacts appear without build-like artifacts, without exposing source diffs.
Tool
explain_change_evidence: inspect local Git state and bounded top-level evidence names.
Safety
- Local paths only, bounded by
EVIDENCE_DIFF_ROOTand realpath checks. - Returns only counts, coarse categories, coarse branch state, and commit dates.
- Never returns source diffs, evidence filenames, branch names, file paths from Git output, commit subjects, authors, command output, file contents, or secrets.
- Does not execute tests, builds, or arbitrary project commands.
- This is an evidence explanation aid, not a code review or CI oracle.
Run
npm install
npm run build
node dist/index.js
