# mergewarden [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/sjh9714/mergewarden  
**GitHub Stars:** 14  
**npm Downloads (last month):** 61  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mergewarden

## Description
Check whether a coding agent's changes stayed inside the scope it was given.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mergewarden": {
    "command": "npx",
    "args": ["--yes","mergewarden@0.10.4"]
  }
}
```

## Documentation

## What mergewarden MCP server does

The supported product behavior centers on reviewing public GitHub pull requests before code review. It identifies missing issue references, descriptions with little prose, unused pull-request templates, and changes exceeding 50 files or 1,500 changed lines.

A separate detailed scan checks four deterministic security areas: workflow permission changes and risky triggers, modifications to files that guide coding agents, pull-request text passed into workflow prompts, and package-manifest changes to install-time lifecycle scripts.

## How it works

MergeWarden reads public GitHub data directly. Its browser queue examines the latest 30 open pull-request summaries, excludes trusted repository roles, base-repository branches, and known maintenance automation, then loads details for no more than 10 external pull requests. Rows are ordered by observable facts rather than an AI-generated judgment.

The queue reads repository metadata and the base branch's pull-request template. The detailed scan reads only files needed by its deterministic rules and evaluates policy from the exact base commit, not the untrusted pull-request head. The analysis does not call a language model, execute code, or clone the target repository.

## Setup and configuration

A browser user can paste `owner/repository` or a full public GitHub repository URL into the review queue. The CLI can run a larger authenticated queue with `GH_TOKEN`, or scan a pull request directly with `npx --yes mergewarden@0.10.4 scan <url>`.

A GitHub Action can run the detailed risk check on `pull_request` events. Its example requests `contents: read` and `pull-requests: write`, and supports `comment: auto`. For immutable Action usage, the documentation recommends pinning a release commit.

## Tools and capabilities

The documented MergeWarden interfaces support:

- Reviewing public pull-request queues for missing context.
- Scanning a pull request for deterministic security findings.
- Running queue triage from a terminal.
- Automating detailed scans through GitHub Actions.
- Updating one actionable pull-request comment when the Action is configured to do so.

## Limitations and notes

MergeWarden never closes, labels, scores, or comments on a pull request through the review queue. It does not classify contributions as spam, low quality, or AI-generated. Browser limits are explicit: sampling 30 summaries or exceeding the 10-detail limit produces an incomplete queue rather than a complete result.

The web app has no backend or telemetry and communicates directly with the public GitHub API. The Action and web app do not execute pull-request code. Incomplete evidence is reported as incomplete, not as a pass. The mergewarden MCP server should therefore be evaluated against its unspecified MCP interface before integration.

_Full upstream README: https://allmcps.com/mcp/mergewarden/readme_