hook-hero vs Hackle
hook-hero is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
hook-hero is a plugin bundle for AI coding tools published by Le Zhang. No marketplace we read lists it any more. Hackle is an MCP server published by hackle-io. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-20. 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 |  Hackle | |
|---|---|---|
| Community marketplace damahua/claude-code-hook-hero | Removed on 2026-10-20 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:b45e8e1c6390 Forks (GitHub): 3 Pulls (Docker Hub): 16 164 Stars (Docker Hub): 0 Stars (GitHub): 3 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 | hook-herono longer listed · | Hackle |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 5 | 3 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 16 164 |
| Forks (GitHub) (differs) | 0 | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 19 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 14 | Not published |
| Parts of the bundle (differs) | 16 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/damahua/claude-code-hook-hero | github.com/hackle-io/hackle-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
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 hook-hero
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
OpenTelemetry observability for Claude Code sessions. Captures tool calls, LLM invocations, token usage, and errors as OTel traces. Send telemetry to Dash0 or any…
-
Flightdeck observability for Claude Code sessions — streams every LLM call, tool use, and MCP event to a self-hosted dashboard.
-
Turn-level governance observability for Claude Code transcripts. Local-first, no LLM inside.
-
Langfuse observability plugin for Claude Code — captures and exports traces, spans, and session telemetry from Claude Code to Langfuse for LLM monitoring, debugging, and evaluation
-
Track Claude Code usage, rejections, and session stats in one dashboard.
-
Automatically trace Claude Code conversations to Braintrust. Captures user messages, assistant responses, and tool calls for observability.
What each says it does
hook-hero
Agent session telemetry for Claude Code — captures structured events from 14 hook lifecycle events with msgpack compression, optional encryption, and a real-time terminal dashboard.
Hackle
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
How to run each
hook-hero
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Hackle As a remote MCP server
claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hackle has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of hook-hero publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of hook-hero publish no settings it asks for, so we do not compare settings.
What it can do: hook-hero · What it can do: Hackle · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.