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.413 npm2ISC
- AlicenseNot gradedqualityDmaintenanceEnables Claude to analyze GitHub repositories with tools for health scoring, contributor analysis, issue tracking, code search, and more.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query GitHub repository insights such as health, commit activity, stale pull requests, contributor stats, releases, and issue backlogs through MCP tools.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.429 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.26 npmMIT
TDQS
A4.4/5.0
Scored across 8 tools
Disambiguation4/5
Most tools have clearly distinct purposes, and the descriptions include explicit cross-references to prevent misuse. However, get_repo_health vs get_health_score and check_best_practices vs get_health_score have partially overlapping outputs (scores/grades/heuristics), which could cause an agent to pick the wrong one without careful reading.
Naming Consistency4/5
All tools follow a verb_noun pattern, and verbs loosely map to action types: analyze for vulnerability scanning, check for status/best practices, get for metrics/metadata, and compare for ranking. The main inconsistency is that get_repo_health and get_health_score sound very similar despite returning different kinds of data, and check_best_practices could plausibly have been named get_best_practices.
Tool Count5/5
Eight tools is well-scoped for a GitHub repository health/analytics server. Each tool covers a distinct analysis dimension, and none feel redundant or extraneous.
Completeness5/5
The tool set covers the domain thoroughly: raw metadata, CI status, security scanning (CodeQL and Dependabot), best practices, DORA metrics, composite health scoring, and multi-repo comparison. No major workflow dead ends or obvious missing operations for a read-heavy health assessment server are apparent.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive