commit-check MCP server
Validate commit messages, branch names, author info, push safety, and repo state.
A94/100grade A
Adoption
Growing
1 stars47 downloads/wk
Reviews
Write oneNobody 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.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan6 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add commit-check-mcp -- uvx commit-check-mcp
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, Claude Desktop or Cursor 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 8 days ago (2026-09-13). The latest release is v0.1.11.