enclave vs Hackle
enclave is an MCP server published by AVGVSTVS96. Marketplaces we read that list it: 1 (Official MCP Registry). 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-11-09. 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 |  enclave |  Hackle |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.13 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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 648 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 | enclave | Hackle |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 3 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 16 648 |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release (differs) | 2026-11-03 | Not published |
| Where it runs (differs) | On your machine (enclave-link) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 19 |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/avgvstvs96/enclave | github.com/hackle-io/hackle-mcp |
| Changes in the last 7 days (differs) | 10 | 0 |
| First seen (differs) | 2026-11-03 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 42 h ago returned HTTP 405 |
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
enclave
Your agent asks for a password by one-time link, not in chat, and uses it without seeing it.
Hackle
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
How to run each
enclave As a local MCP server: npm package
claude mcp add --transport stdio enclave -- npx -y enclave-link mcpHackle 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 enclave publish no list of tools, so we do not compare tools.
Settings each asks for
Only enclave asks for
ENCLAVE_FROMENCLAVE_HOMEENCLAVE_RELAY
Only Hackle asks for
API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: enclave · What it can do: Hackle · Compare two other plugins
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.