Tags: commit-check/commit-check-mcp
Tags
fix: add mcp-name ownership proof to README for MCP Registry publicat… …ion (#22) The MCP Registry requires the server name to appear as 'mcp-name: io.github.commit-check/commit-check-mcp' in the PyPI package README as proof of ownership. Without this line, the registry validation fails. Placed at the bottom of README with HTML comments explaining its purpose, to prevent accidental deletion.
fix: resolve MCP registry publish race condition by merging into publ… …ish workflow (#21) The MCP registry publish workflow (publish-mcp-registry.yml) ran concurrently with the PyPI publish workflow on release events. The MCP Registry validates that the PyPI package exists before accepting the server.json, but due to the race condition it got a 404. Fix by merging the MCP registry publishing as a dependent job (needs: publish) into publish.yml, ensuring PyPI upload completes before the MCP Registry validation runs. Removed the standalone publish-mcp-registry.yml to avoid duplicate triggers.
feat: improve MCP tool descriptions to address Glama score issues (#15) Address the following scoring dimensions flagged by Glama.ai: - Behavior: All tools now explicitly state 'Read-only' nature - Parameters: Every tool documents config, repo_path, config_path params - Completeness: Return value format (status + per-check results) described - Usage Guidelines: Each tool explains when to use vs sibling tools - Purpose: Retained clear verb+resource structure Tools updated: server_health, validate_commit_message, validate_branch_name, validate_author_info, validate_push_safety, validate_commit_context, validate_repository_state, describe_validation_rules