Hackle vs Task Scheduler
Hackle is an MCP server published by hackle-io. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Task Scheduler is an MCP server published by memoryapi.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  Hackle | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:b45e8e1c6390 Forks (GitHub): 3 Pulls (Docker Hub): 16 224 Stars (Docker Hub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
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 | Hackle | Task Scheduler |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 16 224 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (cron.memoryapi.org/mcp) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 19 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hackle-io/hackle-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-22 | Responded 11 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
Hackle
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
Task Scheduler
Schedule and manage recurring or one-shot tasks
How to run each
Hackle As a remote MCP server
claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcpTask Scheduler As a remote MCP server
claude mcp add --transport http cron https://cron.memoryapi.org/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of Task Scheduler responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of Task Scheduler publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Task Scheduler publish no settings it asks for, so we do not compare settings.
What it can do: Hackle · What it can do: Task Scheduler · 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.