pagerduty vs BuildPulse
pagerduty is a plugin bundle for AI coding tools published by PagerDuty. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). BuildPulse is an MCP server published by BuildPulseLLC. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  pagerduty |  BuildPulse |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.7 Downloads/month (npm): 486 Downloads/week (npm): 44 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 | pagerduty | BuildPulse |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 7 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.pagerduty.com/mcp) | Remote server (mcp.buildpulse.io/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/pagerduty/claude-code-plugins | github.com/buildpulsellc/buildpulse-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 30 h ago, requires a key | not checked yet |
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
pagerduty
Enhance code quality and security through PagerDuty risk scoring and incident correlation. Score pre-commit diffs against historical incident data and surface deployment risk before you ship.
BuildPulse
BuildPulse CI test analytics for AI agents — flaky tests, CI failures, flakiness, and code coverage.
How to run each
pagerduty As a Claude Code plugin
/plugin install pagerduty@claude-plugins-officialBuildPulse As a remote MCP server
claude mcp add --transport http buildpulse-mcp https://mcp.buildpulse.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: BUILDPULSE_TOKEN (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only pagerduty 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 pagerduty publish no settings it asks for, so we do not compare settings.
What it can do: pagerduty · What it can do: BuildPulse · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.