blackduck-sca-mcp vs ProjectPulse MCP
blackduck-sca-mcp is an MCP server published by blackducksoftware. Marketplaces we read that list it: 1 (PyPI (MCP servers)). 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-10-30. 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 |  blackduck-sca-mcp |  ProjectPulse MCP |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.9.8 Downloads/month (PyPI): 445 Downloads/week (PyPI): 275 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.10.0 Downloads/month (npm): 1 371 Downloads/week (npm): 270 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.10.0 Downloads/month (npm): 1 371 Downloads/week (npm): 270 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 | blackduck-sca-mcp | ProjectPulse MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 3 (better) | 1 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-24 (better) | 2026-10-18 (worse) |
| Where it runs (differs) | On your machine (blackduck-sca-mcp) | 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/blackducksoftware/sca-mcp | github.com/alexbypa/github-projectpulse-mcp |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
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
blackduck-sca-mcp
A agentic tool for handling and orchestrating Black Duck SCA products.
ProjectPulse MCP
Monitor GitHub repo health, DORA metrics and CI signals from your AI assistant.
How to run each
blackduck-sca-mcp
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 blackduck-sca-mcp publish no settings it asks for, so we do not compare settings.
What it can do: blackduck-sca-mcp · What it can do: ProjectPulse MCP · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.