git-hooks-manager vs ProjectPulse MCP
git-hooks-manager is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑10.
git-hooks-manager is a plugin bundle for AI coding tools published by GLINCKER Team. No marketplace we read lists it any more. ProjectPulse MCP is an MCP server published by alexbypa. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-12. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ProjectPulse MCP | |
|---|---|---|
| Community marketplace glincker/claude-code-marketplace | Removed on 2026-11-10 Version: 1.0.0 Forks (GitHub): 6 Stars (GitHub): 38 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.10.0 Downloads/month (npm): 650 Downloads/week (npm): 169 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.10.0 Downloads/month (npm): 650 Downloads/week (npm): 169 Forks (GitHub): 0 Stars (GitHub): 1 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 | git-hooks-managerno longer listed · | ProjectPulse MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 38 | 1 |
| Forks (GitHub) (differs) | 6 | 0 |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (projectpulse-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/glincker/claude-code-marketplace | github.com/alexbypa/github-projectpulse-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of git-hooks-manager
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Git Hooks - Event-driven automation hooks
-
Sets up and manages Husky Git hooks by configuring pre-commit hooks, establishing commit message standards, integrating with linting tools, and ensuring code quality on commits.
-
Turn a tangled working tree into a clean, reviewable commit series. Three deterministic stdlib scripts over git: a series planner that groups changes into commits in build-safe…
-
Commands for git commit workflows including commit, push, and PR creation
-
Advanced commit workflows with smart staging and push automation
-
Commands for git commit workflows including commit, push, and PR creation
What each says it does
git-hooks-manager
Setup git hooks for pre-commit, pre-push automation
ProjectPulse MCP
Monitor GitHub repo health, DORA metrics and CI signals from your AI assistant.
How to run each
git-hooks-manager
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 git-hooks-manager publish no settings it asks for, so we do not compare settings.
What it can do: git-hooks-manager · What it can do: ProjectPulse MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.