Ext Ops Panel
Open dashboard
Comparison

Musts vs commit-check MCP

Musts is a plugin bundle for AI coding tools published by David Collado. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
MarketplaceMustscommit-check MCP
Community marketplace bitomule/musts Listed
Version: not stated
No figure published
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

Musts vs commit-check MCP
FactMustscommit-check MCP
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
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
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/bitomule/mustsgithub.com/commit-check/commit-check-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-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

Musts

In its own words, on Community GitHub marketplaces:

Bundles the musts skill and a PreToolUse hook that runs `musts validate` before each `git commit` and blocks it until the loop is clean.

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

Musts As a Claude Code plugin

Claude Code
/plugin marketplace add bitomule/musts
/plugin install musts@musts

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: Musts · What it can do: commit-check MCP · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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