NoCrash vs net.hookpulse/hookpulse
NoCrash is an MCP server published by nocrash.io. Marketplaces we read that list it: 1 (Official MCP Registry). net.hookpulse/hookpulse is an MCP server published by hookpulse.net. 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 |  NoCrash |  net.hookpulse/hookpulse |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 1.0.1 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 | NoCrash | net.hookpulse/hookpulse |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (nocrash.io/mcp) | Remote server (hookpulse.net/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/wrpbr/hookpulse |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 301 (6 days ago) | Responded 34 h ago |
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
NoCrash
Know when your n8n workflows, URLs, and AI apps break, before your customers do.
net.hookpulse/hookpulse
Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.
How to run each
NoCrash As a remote MCP server
claude mcp add --transport http nocrash https://nocrash.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
net.hookpulse/hookpulse As a remote MCP server
claude mcp add --transport http hookpulse https://hookpulse.net/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of net.hookpulse/hookpulse responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of NoCrash nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: NoCrash · What it can do: net.hookpulse/hookpulse · Compare two other plugins
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.