A
licenseC
qualityC
maintenanceMonitors 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.
1
MIT
projectpulse-mcp
by alexbypa
Related Servers
Alternatives to projectpulse-mcp
Related Servers
- FlicenseAqualityBmaintenanceEnables real-time assessment of GitHub repository health by exposing tools and resources for repository metadata, open issues, recent commits, and GitHub Actions workflow runs, plus prompts for health reports and issue triage.4-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze GitHub repositories, including fetching repository details, searching, and retrieving README content.305 npm2ISC
- AlicenseNot gradedqualityDmaintenanceEnables Claude to analyze GitHub repositories with tools for health scoring, contributor analysis, issue tracking, code search, and more.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to analyze public GitHub repositories directly through tools for repo health scoring, recent commit summaries, good first issue discovery, and semantic Q&A over docs and issues.426 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform GitHub analytics and management tasks, including repository analysis, PR summarization, issue triage, release notes generation, and contributor statistics.44 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI applications to retrieve GitHub repository information, manage issues, and monitor workflow statuses through the GitHub REST API.-
TDQS
A4.6/5.0
Scored across 7 tools
Disambiguation4/5
Each tool has a distinct analytical focus: raw metadata, computed health score, CI status, CodeQL alerts, dependency vulnerabilities, DORA metrics, and multi-repo comparison. The only potential confusion is get_repo_health vs get_health_score, since both names suggest health assessment, though the descriptions clearly separate raw metadata from computed grading.
Naming Consistency5/5
All tool names follow a consistent verb_first snake_case convention with get_, analyze_, check_, and compare_ prefixes. The resource nouns are clear and the naming pattern is predictable across the entire set.
Tool Count5/5
Seven tools is well-scoped for a repository health and analytics MCP server. Each tool provides a meaningful, distinct capability without unnecessary overlap or bloat.
Completeness4/5
The server covers the core analytics surface well: repo metadata, health grading, CI status, dependency security, code scanning, DORA metrics, and cross-repo comparison. Minor gaps exist around contributor/community activity details, but they are not central to the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive