A
licenseNot graded
qualityF
maintenanceComprehensive MCP server for analyzing GitHub pull requests, detecting security vulnerabilities, assessing code quality, and providing risk ratings across multiple languages.
2 npm
MIT
gts-repo-guardian
by planetazuzu
Related Servers
Alternatives to gts-repo-guardian
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server for automated code review of GitHub pull requests. It checks security, quality, and license issues, and provides tools to list, inspect, and review PRs.15 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that analyzes GitHub repositories and automatically generates README.md files. Supports multiple AI providers and offers web, MCP tool, and n8n workflow modes.1Creative Commons Zero v1.0 Universal
- FlicenseNot gradedqualityDmaintenanceMCP server that provides structured briefs for public GitHub repositories, including metadata, key files, release notes, and activity snapshots.-
- AlicenseAqualityBmaintenanceAn MCP server that provides operational tooling over the GitHub API — issue triage, PR review monitoring, repo health audits, and team access reviews.111MIT
- AlicenseAqualityCmaintenanceMCP server that computes a GitHub repo maintenance/abandonment health score from live GitHub data, providing a 0-100 score and verdict via the check_repo_health tool.120 npmMIT
TDQS
A3.5/5.0
Scored across 6 tools
Disambiguation4/5
Most tools are clearly distinct: review, generate README, clean, bulk review, apply improvements, and watch. The main overlap is between clean_repository and apply_improvements, both of which modify a repo, though their stated intents are different enough to be workable.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern, such as review_repository, generate_readme, and watch_repositories. The naming is predictable and makes the action of each tool immediately clear.
Tool Count5/5
Six tools is well within the ideal range for a focused repo management server. Each tool covers a distinct part of the repo guarding workflow without unnecessary bloat.
Completeness4/5
The surface covers core lifecycle needs: review, improve, clean, document, bulk review, and monitor repos. Missing pieces like rollback/revert or report retrieval are minor and can be worked around.
Maintenance
ActivityInactive
ResponsivenessNo issues