isnap-webhooks vs Rootly
isnap-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Rootly is an MCP server published by rootly.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-12. 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 |  Rootly | |
|---|---|---|
| Community marketplace hookdeck/webhook-skills | Listed Version: not stated Forks (GitHub): 16 Stars (GitHub): 101 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.2.4 Downloads/month (PyPI): 4 198 Downloads/week (PyPI): 1 242 Forks (GitHub): 25 Stars (GitHub): 45 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 2.4.0 Downloads/month (PyPI): 4 198 Downloads/week (PyPI): 1 242 Forks (GitHub): 25 Stars (GitHub): 45 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 | isnap-webhooks | Rootly |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 101 (better) | 45 (worse) |
| Forks (GitHub) (differs) | 16 (worse) | 25 (better) |
| Last release (differs) | Not published | 2026-11-01 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/hookdeck/webhook-skills | github.com/rootly-ai-labs/rootly-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-06 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 h ago, requires authentication |
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
isnap-webhooks
Receive and verify iSnap webhooks, which follow the Standard Webhooks specification. Use when setting up an iSnap webhook endpoint, getting the whsec_ signing secret from POST /v1/webhooks, debugging webhook-id / webhook-timestamp / webhook-signature verification, or handling iMessage and SMS line events like message.received, message.delivered, message.failed, reaction.received and line.offline.
Rootly
Incident management, on-call scheduling, and intelligent analysis powered by Rootly.
How to run each
isnap-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install isnap-webhooks@webhook-skillsRootly As a remote MCP server
claude mcp add --transport sse rootly https://mcp.rootly.com/sse --header "Authorization: Bearer <YOUR_TOKEN>"Requires: ROOTLY_API_TOKEN (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Rootly 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 isnap-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: isnap-webhooks · What it can do: Rootly · 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 Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.