Evidence Diff Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Nov 5, 2026

Explain coarse Git and test-build evidence changes without source diff contents. Tools include...

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that explains coarse Git and test/build evidence changes in a project without exposing source diffs.

What you can do
  • Inspect local Git state and bounded top-level evidence names for a project.
  • Report whether a worktree changed, whether uncommitted evidence exists, and whether test-like artifacts appear without build-like artifacts.
  • Return only counts, coarse categories, coarse branch state and commit dates, with no diffs, filenames, paths, commit subjects or authors.
When to use it
Useful when an assistant needs a privacy-preserving hint about whether a repository's working state or test/build evidence has shifted, without reading source changes. Suited to coarse status explanations rather than code review or CI decisions.
Requirements
Runs as a local stdio process installed from the npm package evidence-diff-mcp; the README shows building and running it with Node.js. A root path is bounded by the EVIDENCE_DIFF_ROOT environment variable. No authentication is declared.
Before you install
It reads local Git state, so point EVIDENCE_DIFF_ROOT at the intended project only. It deliberately withholds details, so its output is an explanation aid, not a code review or CI oracle. It does not run tests, builds or project commands.

Installation

In SourceWeft

  1. Open Evidence Diff Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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_ROOT and 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

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit 1e57685

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.