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 gradedqualityCmaintenanceEnables AI assistants to search, inspect, compare, and evaluate GitHub repositories using read-only tools, including topic discovery, repository health scoring, security advisories, dependency audits, and supply-chain risk checks. It returns concise, readable results and can work without a token, with optional authentication for higher rate limits and code search.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze GitHub repositories, including fetching repository details, searching, and retrieving README content.642 npm2ISC
- AlicenseNot gradedqualityDmaintenanceEnables Claude to analyze GitHub repositories with tools for health scoring, contributor analysis, issue tracking, code search, and more.MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to query GitHub repository insights such as health, commit activity, stale pull requests, contributor stats, releases, and issue backlogs through MCP tools.6MIT
- 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.427 npm1MIT
TDQS
A4.4/5.0
Scored across 8 tools
Disambiguation4/5
Each tool targets a distinct analysis area, and the descriptions include explicit 'DO NOT use this for X, use Y instead' guidance that sharply delineates boundaries. However, get_health_score and check_best_practices both emit a 0-100 score with an A-F grade, and compare_repos is essentially a multi-repo wrapper of get_health_score, so a few tools could still be confused at the edges.
Naming Consistency5/5
All eight tools use snake_case with a clear verb_noun structure (analyze_*, get_*, check_*, compare_*). The verb prefixes are chosen sensibly for each operation and the convention is applied uniformly across the set.
Tool Count5/5
Eight tools is well-scoped for a repository health/analysis server, with each tool covering a distinct facet (metadata, CI, DORA, dependencies, code scanning, best practices, health score, comparison). No tool appears redundant or padded.
Completeness4/5
The surface covers a broad analysis lifecycle: raw metadata, CI status, DORA metrics, dependency and code-scanning alerts, best-practice audit, aggregated health scoring, and multi-repo comparison. Minor gaps remain, such as no way to retrieve historical trend snapshots or drill into individual alert details, but core workflows are well covered.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive