pagerduty vs io.github.dusk-network/pituitary
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). io.github.dusk-network/pituitary is an MCP server published by dusk-network. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  io.github.dusk-network/pituitary |
|---|---|---|
| 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: 1.0.0-beta.12 Forks (GitHub): 3 Stars (GitHub): 22 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 | io.github.dusk-network/pituitary |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 7 (worse) | 22 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.pagerduty.com/mcp) | On your machine (https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-darwin-arm64.mcpb) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/pagerduty/claude-code-plugins | github.com/dusk-network/pituitary |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 10 h ago, requires a key | no remote endpoint we check |
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.
io.github.dusk-network/pituitary
Catch spec drift before it catches you. Detect overlap, stale docs, and code drift.
How to run each
pagerduty As a Claude Code plugin
/plugin install pagerduty@claude-plugins-officialio.github.dusk-network/pituitary
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
Neither one's marketplaces publish the settings it asks for.
What it can do: pagerduty · What it can do: io.github.dusk-network/pituitary · 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.