Ext Ops Panel
Open dashboard
Comparison

git-bisect-pr-review vs commit-check MCP

git-bisect-pr-review is a plugin bundle for AI coding tools published by Pierre-louis242. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). commit-check MCP is an MCP server published by commit-check. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacegit-bisect-pr-reviewcommit-check MCP
Claude Code: claude-plugins-community Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.12
Downloads/month (PyPI): 346
Downloads/week (PyPI): 149
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

git-bisect-pr-review vs commit-check MCP
Factgit-bisect-pr-reviewcommit-check MCP
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (commit-check-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/pierre-louis242/git-bisect-pr-reviewgithub.com/commit-check/commit-check-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

git-bisect-pr-review

In its own words, on Claude Code: claude-plugins-community:

Two skills in one plugin: (1) Automated git bisect for regression hunting — establishes boundaries, runs `git bisect run` with reproduction commands, analyzes the culprit commit, and suggests fixes. (2) Structured PR review — loads PR context via `gh` CLI, reviews across five dimensions (code quality, test coverage, security, performance, CI status), posts inline and general comments, handles approvals, and merges with the repo's preferred strategy. Includes safety rails: never merges without user confirmation, never force-pushes to protected branches. Requires `gh` CLI.

commit-check MCP

In its own words, on Official MCP Registry:

Commit policy as code for AI agents: check commit messages, branch names and authors before a push

How to run each

git-bisect-pr-review As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install git-bisect-pr-review@claude-community

commit-check MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio commit-check-mcp -- uvx commit-check-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: git-bisect-pr-review · What it can do: commit-check MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built