incident-response vs Delimit
incident-response is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑07.
incident-response is a plugin bundle for AI coding tools published by Grey Haven Studio. No marketplace we read lists it any more. Delimit is an MCP server published by delimit-ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-13. 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 |  Delimit | |
|---|---|---|
| Community marketplace greyhaven-ai/claude-code-config | Removed on 2026-11-07 Version: 2.1.0 Forks (GitHub): 5 Stars (GitHub): 31 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.10.4 Downloads/month (npm): 5 560 Downloads/week (npm): 2 503 Forks (GitHub): 5 Stars (GitHub): 23 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 4.24.0 Downloads/month (npm): 5 560 Downloads/week (npm): 2 503 Forks (GitHub): 5 Stars (GitHub): 23 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-responseno longer listed · | Delimit |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 31 | 23 |
| Forks (GitHub) | 5 | 5 |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (delimit-cli) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/greyhaven-ai/claude-code-config | github.com/delimit-ai/delimit |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-20 | 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 incident-response
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Production incident management, triage workflows, and automated incident resolution
-
Production incident management, triage workflows, and automated incident resolution
-
Turn incidents and product signals into evidence for the next recovery or product decision.
-
Official incident.io plugins for AI agents: skills for working with [incident.io](https://incident.io/) — incidents, on-call, and investigations — and for authoring the…
-
Full-lifecycle incident management: deploy safety, incident response, on-call management, and retrospectives.
-
Use Resolve for investigations, incidents, and production context.
What each says it does
incident-response
Production incident response system with incident management workflows, intelligent debugging, runbook automation, and postmortem generation. Handles incident detection, triage, mitigation, and learning.
Delimit
One workspace for every AI coding assistant. Shared tasks, memory, and governance.
How to run each
incident-response
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Delimit As a local MCP server: npm package
claude mcp add --transport stdio delimit -- npx -y delimit-cliCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: incident-response · What it can do: Delimit · 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.