commit-check-mcp
OfficialRelated Servers
Alternatives to commit-check-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables dependency, security, and coding convention checks for Python and Java projects via MCP tools. Supports local paths or Git URLs.-
- AlicenseNot gradedqualityCmaintenanceEnables automated code review and GitHub PR commenting through MCP integration.1,032 npm9MIT
- FlicenseNot gradedqualityDmaintenanceMCP server providing commit rules with SemVer and conventional commits format for development teams.-
- FlicenseNot gradedqualityCmaintenanceEnables automated semantic release notes, PR tagging, and changelog verification by integrating GitHub, GitLab, and Jira MCP servers.-
- AlicenseBqualityCmaintenanceEnables automated pull request review, security vulnerability analysis, and code quality improvement suggestions through any MCP client.323 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI clients to inspect Git repository changes, run allowlisted validation commands, and generate Markdown review reports via MCP, with validation disabled by default for security.-
TDQS
Scored across 8 tools
Each tool targets a distinct validation aspect (author, branch, message, push, repo state) and descriptions explicitly cross-reference when to prefer the aggregate validate_commit_context or validate_repository_state. The only real overlap is validate_commit_context duplicating the three single-aspect validators, which is intentional but still leaves an agent a choice point between 'one aspect' and 'aggregate'.
The set follows a clear verb_noun pattern (validate_*, describe_*) with consistent snake_case throughout. The lone deviation is server_health, which is a noun phrase with no verb, though it is a conventional health-check name.
Eight tools is well-scoped for a commit-rule validation server: one discovery tool, five validators covering each aspect plus an aggregate and repo-state check, one push-safety tool, and a health probe. No tool appears redundant beyond the deliberately layered aggregate/single validators.
The surface covers the full pre-commit lifecycle: inspect effective rules, validate message/branch/author individually or together, validate an existing HEAD commit, and check push safety. A minor gap is validating arbitrary historical commits or commit ranges, since validate_repository_state only inspects the latest commit at HEAD.