network-terminal-mcp vs Hackle
network-terminal-mcp is an MCP server published by evgenyzh. Marketplaces we read that list it: 1 (PyPI (MCP servers)). 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-08. 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 |  network-terminal-mcp |  Hackle |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.2.1 Downloads/month (PyPI): 249 Downloads/week (PyPI): 211 Forks (GitHub): 0 Stars (GitHub): 0 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 589 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 | network-terminal-mcp | 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 589 |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release (differs) | 2026-10-31 | Not published |
| Where it runs (differs) | On your machine (network-terminal-mcp) | 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 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/evgenyzh/network-terminal-mcp | github.com/hackle-io/hackle-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 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
network-terminal-mcp
Persistent local terminals for MCP clients, opened with real SSH, Telnet, and serial commands
Hackle
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
How to run each
network-terminal-mcp
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 network-terminal-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of network-terminal-mcp publish no settings it asks for, so we do not compare settings.
What it can do: network-terminal-mcp · What it can do: Hackle · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.