MCP.Market

commit-check MCP server

by commit-check·io.github.commit-check/commit-check-mcp·v0.1.12·1 stars

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

A94/100grade A
What users say
No reviews yet
Be the first
Safety scan
A94/100

not scanned yet

Adoption
Growing

1 stars30 downloads/wk

Reviews

Write one

Nobody has reviewed commit-check MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

commit-check MCP tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How commit-check MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
94/100
higher than 96% of 48,243 servers
GitHub stars
1
more than 65% of 28,706 servers
Downloads a week
30
more than 18% of 12,306 servers with a package

Release history: 2 versions in the registry since 2026-09-10, latest 2026-10-08, typically one every 28 days.

Install commit-check MCP in Claude Code, Cursor or VS Code

claude mcp add commit-check-mcp -- uvx commit-check-mcp
Add to Cursor

What the publisher says

From the commit-check MCP repository's README, as published. We do not edit it. Read it on GitHub

commit-check-mcp

Model Context Protocol (MCP) server for commit-check.

commit-check-mcp exposes commit-check as local MCP tools so an MCP client can validate commit messages, branch names, author info, push safety, and repository state.

Features

This MCP server exposes commit-check validations as MCP tools:

  • server_health — returns server/sdk versions
  • validatecommitmessage — validates a commit message
  • validatebranchname — validates a branch name or the current repo branch
  • validatepushsafety — validates that a push is not a force push (force pushes are always rejected by this tool)
  • validateauthorinfo — validates author name/email or the repo's git author config
  • validatecommitcontext — runs combined checks in one call
  • validaterepositorystate — validates latest commit, current branch, author state, and optional push safety for a repo
  • describevalidationrules — returns the effective config and enabled rules after merging defaults and repo config

All validation tools return the same structured commit-check result shape:

{
  "status": "pass|fail|skip",
  "warnings": 0,
  "checks": [
    {
      "rule_id": "CC001",
      "check": "message",
      "status": "pass|fail|warn|skip",
      "value": "...",
      "error": "...",
      "suggest": "...",
      "fix": "...",
      "docs_url": "https://commit-check.com/rules/#cc001"
    }
  ]
}

ruleid is the stable id of the rule that produced the check and docsurl links to its documentation.

Only fail is a rejection. A check reports skip when it did not run — the author matched ignoreauthors, or there was nothing to check — and the top-level status is skip only when every** check skipped, so a run that validated nothing is never reported as a pass. A check reports warn when the config lists it under warn: the finding is complete, but it does not fail the run, the top-level status stays pass, and warnings counts them.

suggest is the advice a person reads. fix is the corrected value itself, present only when the correction is unambiguous — Fix: add x comes back with "fix": "fix: add x" — and an empty string otherwise, so an agent can apply a non-empty fix as it stands and fall back to suggest when it is empty.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

commit-check MCP: common questions

Is commit-check MCP server safe?
Yes, by our scan: it is graded A (94/100). Read the commit-check MCP safety report
How do I install commit-check MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does commit-check MCP need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is commit-check MCP maintained?
The last commit was 35 days ago (2026-10-01). The latest release is v0.1.12.
How does commit-check MCP compare with other MCP servers?
safety score 94/100 (higher than 96% of 48,243 servers); github stars 1 (more than 65% of 28,706 servers); downloads a week 30 (more than 18% of 12,306 servers with a package). Full comparison.