Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DiffCI

NPM · @DIFFCI.COM/DIFFCI · 2 COMPONENTS

Verification for AI coding agents: runs the tests and checks a change affects, with a receipt.

+9 this week 73 Trust /100

Last scanned (8 hours ago)

Scores higher than 46% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security41
  • Malware scan not yet available for this package.Unverified
  • Known CVEs were checked across the 3 of 4 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 3 of 4 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to DiffCI/core). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1079 tokens (~119/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.60 → 0.3.61 functional
  • 20 Nov 26 +8
    • Known CVEs: unverified → partial ▲ security
    • Dependency health: unverified → partial ▲ functional
  • 19 Nov 26 +7
    • Known CVEs: partial → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: partial → unverified ▼ functional
    • Package version: 0.3.57 → 0.3.60 functional
    • Package version: 0.3.57 → 0.3.59 functional
    • Package version: 0.3.57 → 0.3.58 functional
  • 18 Nov 26 −7
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: unverified → partial ▲ security
    • Dependency health: unverified → partial ▲ functional
    • Package version: 0.3.54 → 0.3.57 functional
    • Package version: 0.3.54 → 0.3.56 functional
    • Package version: 0.3.54 → 0.3.55 functional
  • 17 Nov 26 −8
    • Known CVEs: partial → unverified ▼ security
    • Stability: 0.97 → pass security
    • Dependency health: partial → unverified ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Package version: 0.3.51 → 0.3.54 functional
    • Package version: 0.3.51 → 0.3.53 functional
    • Package version: 0.3.51 → 0.3.52 functional
  • 16 Nov 26 +24
    • Stability: 0.93 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Dependency health: unverified → partial ▲ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.3.45 → 0.3.51 functional
    • Package version: 0.3.45 → 0.3.50 functional
    • Package version: 0.3.45 → 0.3.49 functional
    • Package version: 0.3.45 → 0.3.48 functional
  • 15 Nov 26 −23
    • Known CVEs: partial → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: partial → unverified ▼ functional
    • Package version: 0.3.43 → 0.3.45 functional
    • Package version: 0.3.43 → 0.3.44 functional
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.3.42 → 0.3.43 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Analysed npm/@diffci.com/diffci@0.3.61

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo DiffCI/core
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/DiffCI/core/.github/workflows/release-cli.yml@refs/tags/cli-release-v0.3.61
Rekor log index 4045867188
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d7a5840f5952aae48d645c7e361d01c8c34a34be9adb82bcf5536f1973357cb9da05785322b2d93bf3efc57996522c51b6cc04c39f07960799c79c173

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Stale 2
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,079 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
diffci_changed_files ~67

List staged, unstaged and non-ignored untracked changed paths relative to HEAD, with a snapshot identity. Builds no dependency graph and runs no tests.

NameTypeReqDescription
repostring–Absolute repository path; defaults to server working directory. Always pass the edited repository when using a plugin.

No output schema declared.

No examples provided.

diffci_check ~149

Analyze the repository, run inferred full and selected test commands when available, and report paired runtime. No report is uploaded. The run is counted with the repository name unless the user chose count-only; DO_NOT_TRACK=1 stops counting.

NameTypeReqDescription
basestring–Optional base commit SHA.
headstring–Optional head commit SHA.
jsonboolean–Print the full JSON observation report.
quietboolean–Suppress the human summary.
redactPathsboolean–Replace paths in the analysis result with stable digests. Workflow findings and some fallback details can still name files.
repostring–Repository path. Defaults to the MCP server working directory.

No output schema declared.

No examples provided.

diffci_explain_selection ~181

Inspect current staged, unstaged and non-ignored untracked changes and return a snapshot-bound affected-test plan and fallback reasons. Runs no tests; a plan is not a passing receipt. With scope "staged" or "paths", plans HEAD plus only the index or only the given files in a temporary worktree, and returns the one `diffci verify --staged`/`--paths` command to run; use it before a commit when other sessions share the checkout.

NameTypeReqDescription
pathsarray–Repository-relative files for scope "paths".
repostring–Absolute repository path; defaults to server working directory. Always pass the edited repository when using a plugin.
scopestring–working-tree (default): every uncommitted change. staged: HEAD plus the index only. paths: HEAD plus only `paths`.

No output schema declared.

No examples provided.

diffci_init ~174

Seed a repository with DiffCI agent instruction files, MCP server configs, the diffci-verify skill and the pre-push hook.

NameTypeReqDescription
forceboolean–Overwrite existing instruction files.
hookboolean–Install the Git pre-push hook that verifies the commits being pushed (default true).
mcpboolean–Register the DiffCI MCP server in .mcp.json and .cursor/mcp.json (default true).
repostring–Repository path. Defaults to the MCP server working directory.
skillboolean–Add the diffci-verify skill to .claude/skills (default true).
verificationWorkflowboolean–Also add the blocking GitHub Actions verification workflow.
workflowboolean–Also add the non-blocking GitHub Actions observer workflow.

No output schema declared.

No examples provided.

diffci_run_affected_tests ~69

Reanalyze and verify the current working-tree snapshot with affected tests or conservative full fallback. Required CI remains authoritative.

NameTypeReqDescription
repostring–Absolute repository path; defaults to server working directory. Always pass the edited repository when using a plugin.
timeoutMsnumber––

No output schema declared.

No examples provided.

diffci_select_tests ~180

Inspect current staged, unstaged and non-ignored untracked changes and return a snapshot-bound affected-test plan and fallback reasons. Runs no tests; a plan is not a passing receipt. With scope "staged" or "paths", plans HEAD plus only the index or only the given files in a temporary worktree, and returns the one `diffci verify --staged`/`--paths` command to run; use it before a commit when other sessions share the checkout.

NameTypeReqDescription
pathsarray–Repository-relative files for scope "paths".
repostring–Absolute repository path; defaults to server working directory. Always pass the edited repository when using a plugin.
scopestring–working-tree (default): every uncommitted change. staged: HEAD plus the index only. paths: HEAD plus only `paths`.

No output schema declared.

No examples provided.

diffci_verify ~126

Verify a clean commit range and return a receipt bound to the checked-out head commit. Resolves the CI event range automatically when base and head are omitted.

NameTypeReqDescription
basestring–Optional base commit SHA. Must be paired with head.
headstring–Optional head commit SHA. Must be paired with base and match checked-out HEAD.
redactPathsboolean–Replace paths with stable digests in analysis.
repostring–Repository path. Defaults to the MCP server working directory.
timeoutMsnumber–Maximum verification-command runtime in milliseconds.

No output schema declared.

No examples provided.

diffci_verify_changed ~89

Verify the current staged, unstaged, and non-ignored untracked changes. Fails closed unless the exact working-tree snapshot passes selected or full fallback verification.

NameTypeReqDescription
redactPathsboolean–Replace paths with stable digests in analysis.
repostring–Repository path. Defaults to the MCP server working directory.
timeoutMsnumber–Maximum verification-command runtime in milliseconds.

No output schema declared.

No examples provided.

diffci_verify_workflow ~44

Check that a DiffCI GitHub Actions job cannot affect the rest of CI.

NameTypeReqDescription
repostring–Repository path. Defaults to the MCP server working directory.

No output schema declared.

No examples provided.

Install

How do I install the DiffCI MCP server?

DiffCI runs locally as an npm package, launched with npx -y @diffci.com/diffci mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @diffci.com/diffci

# add to Claude Code
claude mcp add diffci-diffci -- npx -y @diffci.com/diffci mcp
Common questions

What is the DiffCI MCP server?

DiffCI is an MCP server listed in the public MCP registry as io.github.DiffCI/diffci. Verification for AI coding agents: runs the tests and checks a change affects, with a receipt. This page covers its npm package (@diffci.com/diffci).

Is the DiffCI MCP server safe to use?

DiffCI scores 73 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DiffCI MCP server expose?

DiffCI exposes 9 tools: diffci_changed_files, diffci_select_tests, diffci_explain_selection, diffci_run_affected_tests, diffci_verify, and 4 more. Their descriptions and schemas cost roughly 1,079 tokens of context every time the server is loaded.

Is the DiffCI MCP server still maintained?

DiffCI is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the DiffCI MCP server under?

DiffCI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the DiffCI MCP server?

VerifyMCP ran 15 checks on DiffCI, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about DiffCI: Malware scan. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.