Commit Check MCP vs Wisegit
A side-by-side look at the Commit Check MCP and Wisegit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Commit Check MCP for version control work as a local process; choose Wisegit for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Commit Check MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
validate_commit_message, validate_branch_name, validate_author_info.
Choose Wisegit when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_file_decisions, get_freeze_score, get_function_history.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 53/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 8 | 11 |
| Full listing | View Commit Check MCP | View Wisegit |
Tools & capabilities
Commit Check MCP tools 8
validate_commit_messagemessagevalidate_branch_namebranch?validate_author_infoauthor_name?` `author_email?validate_commit_contextmessage?` `branch?` `author_name?` `author_email?validate_push_safetypush_refs?` — pre-push lines; omit to compare the branch with its upstreamvalidate_repository_stateinclude_message` `include_branch` `include_author` (default `true`), `include_push` (default `false`)describe_validation_rules—server_health—
Wisegit tools 11
get_file_decisionsDecision manifest for a file — freeze scores, intent history, recovery levels, override statusget_freeze_scoreScore + signal breakdown for a specific functionget_function_historyFull chronological decision timeline for a functionget_theory_gapsFunctions with unrecoverable rationale (inactive authors, timeline gaps)get_branch_contextBranch merge history — what was migrated and whysearch_decisionsSearch past decisions by keyword across the entire repocreate_overrideOverride a frozen function (user approves in Claude Code UI)extract_intentExtract intent for NOISE commits using the host LLM — no Ollama neededfind_similar_functionsSearch for existing functions that solve a similar problem before writing new codepredict_impactPredict what functions will break if a given function is modifiedget_codebase_conventionsExtract coding conventions for a file's neighborhood
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Commit Check MCP
{
"mcpServers": {
"commit-check-mcp": {
"command": "uvx",
"args": [
"commit-check-mcp"
]
}
}
}
Wisegit
{
"mcpServers": {
"wisegit": {
"command": "npx",
"args": [
"-y",
"@sandip124/wisegit"
]
}
}
}
Frequently asked questions
Commit Check MCP is categorized under Version Control and uses a local stdio subprocess. Wisegit belongs to Version Control and uses a local stdio subprocess. Pick Commit Check MCP for version control work and Wisegit for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Commit Check MCP is listed as free. Auth: no auth required. Wisegit has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add commit-check-mcp and wisegit as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Commit Check MCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Wisegit has 51/100 (Good) with 1 views, 0 installs and 1 GitHub stars.