repo-doctorofficial
A
licenseNot graded
qualityC
maintenanceMCP server that produces scored, evidence-cited audits of public GitHub repos via tools for fetching metadata, reading files, scanning git history, and checking hygiene.
MIT
x402-repohealth-mcp
by liminalpepe
Related Servers
Alternatives to x402-repohealth-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that checks npm and PyPI package health, providing maintenance signals, version info, CVE counts, and alternative suggestions.MIT
- FlicenseAqualityDmaintenanceMCP server for automated GitHub repository quality management, enabling review, README generation, cleanup, and monitoring.6-
- AlicenseAqualityBmaintenanceAn MCP server that provides operational tooling over the GitHub API — issue triage, PR review monitoring, repo health audits, and team access reviews.111MIT
- AlicenseAqualityBmaintenanceMCP server that finds beginner-friendly GitHub issues ranked by likelihood of successful contribution, with repo health scoring and issue status checks via the GitHub API.4MIT
- AlicenseCqualityCmaintenanceMonitors and analyzes GitHub repository health by detecting stale branches, old pull requests, unresponsive issues, and security alerts. Integrates with MCP-compatible AI assistants and automation tools.1MIT
TDQS
A4.4/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly and specifically defined, making it unambiguous for agents.
Naming Consistency5/5
The single tool name follows a clean verb_noun pattern ('check_repo_health'), which is internally consistent. With only one tool, there are no conflicting conventions.
Tool Count3/5
The server has exactly one tool, which feels thin for a typical server but is justified by its narrow, single-purpose scope. It is borderline, as 1-2 tools are on the edge of being too few.
Completeness5/5
The tool covers the entire domain of repo health assessment, providing a score, verdict, and reasoning based on all relevant GitHub data. There are no obvious gaps for the stated purpose.
Maintenance
ActivitySlowing
ResponsivenessNo issues