incident.io vs notifyd
incident.io is a plugin bundle for AI coding tools published by incident-io. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). notifyd is an MCP server published by rmzlb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  incident.io |  notifyd |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 1.20261015.672 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 1.20261015.672 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Forks (GitHub): 2 Stars (GitHub): 17 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 | incident.io | notifyd |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 2 (worse) | 17 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 2 (better) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (mcp.incident.io/mcp) | On your machine (ghcr.io/rmzlb/notifyd:0.4.0) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 3 |
| Parts of the bundle (differs) | 12 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/incident-io/skills | github.com/rmzlb/notifyd |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days 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
incident.io
Work with incident.io from Claude: respond to and investigate incidents, check on-call schedules and escalations, and author the runbooks, skills and architecture docs that incident.io investigations draw on. Bundles the official incident.io MCP server (OAuth on first use).
notifyd
Operate a self-hosted notifyd instance: digest, jobs, retries, suppressions, projects, test sends.
How to run each
incident.io As a Claude Code plugin
/plugin install incident-io@claude-plugins-officialnotifyd
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: ADMIN_API_KEY (secret), DATABASE_URL (secret), JWT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only incident.io 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 incident.io publish no settings it asks for, so we do not compare settings.
What it can do: incident.io · What it can do: notifyd · 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/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.