ProjectPulse MCP
io-github-alexbypa-github-projectpulse-mcp declares 8 capabilities across 8 tools, with 1 critical issue.
Issues
8 of 8 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
check_ci_status | read |
declared |
get_repo_health | read |
declared |
analyze_dependencies | read |
declared |
analyze_code_scanning | read |
declared |
get_health_score | read |
inferred |
get_dora_metrics | read |
declared |
compare_repos | read |
declared |
check_best_practices | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-14 | 14 | tools/list answered by the npm package projectpulse-mcp@1.8.4 (published to npm as projectpulse-mcp, listed in the official MCP registry as io.github.alexbypa/github-projectpulse-mcp 1.8.4), run in an isolated container with no network access and placeholder credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.