ProjectPulse MCP vs GitLumen MCP
ProjectPulse MCP is an MCP server published by alexbypa. Marketplaces we read that list it: 1 (Official MCP Registry). GitLumen MCP is an MCP server published by gitlumen-team. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ProjectPulse MCP |  GitLumen MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.10.0 Downloads/month (npm): 1 288 Downloads/week (npm): 117 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ProjectPulse MCP | GitLumen MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-18 | Not published |
| Where it runs (differs) | On your machine (projectpulse-mcp) | Remote server (mcp-github-screen.gitlumen.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/alexbypa/github-projectpulse-mcp | github.com/gitlumen-team/gitlumen-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-13 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ProjectPulse MCP
Monitor GitHub repo health, DORA metrics and CI signals from your AI assistant.
GitLumen MCP
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
How to run each
ProjectPulse MCP As a local MCP server: npm package
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio github-projectpulse-mcp -- npx -y projectpulse-mcpRequires: GITHUB_TOKEN (secret)
GitLumen MCP As a remote MCP server
claude mcp add --transport http gitlumen-mcp https://mcp-github-screen.gitlumen.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitLumen MCP has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of GitLumen MCP publish no settings it asks for, so we do not compare settings.
What it can do: ProjectPulse MCP · What it can do: GitLumen MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.