MCP GitHub Validator
Related Servers
Alternatives to MCP GitHub Validator
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA lightweight, configurable server that fetches coding guidelines, security rules, and validation patterns from external sources to help development teams maintain code quality standards in WordPress projects.35MIT
- FlicenseNot gradedqualityDmaintenanceA TypeScript MCP server that validates codebases against configurable rules. It analyzes files for violations and generates JSON reports, supporting custom rule definitions and file extensions.-
- FlicenseAqualityCmaintenanceA deterministic, network-free MCP server for validating repository release hygiene and version alignment in local projects. It enables automated repository health checks and generates standardized release checklists based on project state.1-
- FlicenseAqualityDmaintenanceMCP server for automated GitHub repository quality management, enabling review, README generation, cleanup, and monitoring.6-
- FlicenseCqualityDmaintenanceA configurable MCP server for managing multiple GitHub repositories, branches, pull requests, and files, with built-in company documentation and validation.3-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enforces repository governance rules for AI coding agents, providing tools to validate plans, diffs, and scan for architectural and safety violations.1MIT
TDQS
Scored across 5 tools
Tools are mostly distinct: list_rules shows available validations, validate_repo and validate_all_repos are clearly scoped by single vs. batch, and list_react_repos/get_repo_structure serve supporting roles. The two validation tools could overlap in purpose but are differentiated by their descriptions.
All tools follow a consistent verb_noun pattern: list_rules, validate_repo, validate_all_repos, list_react_repos, get_repo_structure. The naming is predictable and easy to navigate.
With 5 tools, the server is well-scoped for its stated purpose of validating React repositories. Each tool has a clear role, and the count feels neither thin nor bloated.
The tool set covers the core workflow: list rules, list React repos, inspect structure, validate single or multiple repos. Minor gaps like rule management (add/update/delete) or a dedicated get-validation-history tool exist, but these are not essential for the primary validation use case.