io.github.sjh9714/mergewarden
NPM · MERGEWARDEN-MCP
Check whether a coding agent's changes stayed inside the scope it was given.
Available components
Last scanned (6 minutes ago)
Scores higher than 98% of npm servers
Category Security
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sjh9714/mergewarden). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 75 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 263 tokens (~263/item across 1 items; 1 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → pass ▲ functional
- 4 Nov 26 0
- Security disclosure: pass → unverified ▼ functional
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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 5 Nov 2026 · Analysed npm/mergewarden-mcp@0.9.0
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 | sjh9714/mergewarden |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sjh9714/mergewarden/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 2281538135 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:45f5157deef50cecbc869acd0e5b582a3c0628deb763b7fa25d6f6e3fd51c44fd9119dd865980c48318efc0e7fcc7e0696ad22d5f50c518c68fdb507d |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_change_scope Check whether changes stayed inside their declared scope ~263
Compare the files a change actually touched against the paths it was supposed to touch, and report anything outside them. Also flags edits to agent-instruction files (AGENTS.md, CLAUDE.md, .mcp.json and similar), which change how every future agent run in the repository behaves. Use this before opening a pull request. Get changedPaths from `git diff --name-only` against the branch point. It runs the same engine as the MergeWarden GitHub Action on the same default policy, so a clean result here is what the gate will report. Deterministic and offline: no network, no token, no model call. Only checks decidable from paths — workflow permissions and dependency scripts need file contents and are not covered here.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedPaths | array | yes | Glob paths the change was scoped to, e.g. ['src/auth/**', 'test/auth/**']. Take these from what the user actually asked for. |
| blockedPaths | array | – | Glob paths the change was explicitly told not to touch. |
| changedPaths | array | yes | Repository-relative paths actually changed, from `git diff --name-only`. |
| task | string | – | One line describing what was asked for. Recorded verbatim, never interpreted. |
No output schema declared.
No examples provided.
How do I install the io.github.sjh9714/mergewarden MCP server?
io.github.sjh9714/mergewarden runs locally as an npm package, launched with npx -y mergewarden-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 · mergewarden-mcp
claude mcp add sjh9714-mergewarden -- npx -y mergewarden-mcp
What is the io.github.sjh9714/mergewarden MCP server?
io.github.sjh9714/mergewarden is an MCP server listed in the public MCP registry as io.github.sjh9714/mergewarden. Check whether a coding agent's changes stayed inside the scope it was given. This page covers its npm package (mergewarden-mcp).
Is the io.github.sjh9714/mergewarden MCP server safe to use?
io.github.sjh9714/mergewarden scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.sjh9714/mergewarden MCP server expose?
io.github.sjh9714/mergewarden exposes 1 tool: check_change_scope. Their descriptions and schemas cost roughly 263 tokens of context every time the server is loaded.
Is the io.github.sjh9714/mergewarden MCP server still maintained?
io.github.sjh9714/mergewarden is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.sjh9714/mergewarden MCP server under?
io.github.sjh9714/mergewarden declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.