Hackle vs Anzctr
Hackle is an MCP server published by hackle-io. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Anzctr is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |  Anzctr |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:b45e8e1c6390 Forks (GitHub): 3 Pulls (Docker Hub): 16 668 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 | Anzctr |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 16 668 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-30 |
| Where it runs (differs) | Remote server or your machine | Remote server (gateway.pipeworx.io/anzctr/mcp) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 19 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hackle-io/hackle-mcp | github.com/pipeworx-io/mcp-anzctr |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 20 h ago | Status out of date: last check 38 h ago returned HTTP 200 |
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.
Anzctr
ANZCTR — the Australian New Zealand Clinical Trials Registry (anzctr.org.au, run by the NHMRC…
How to run each
Hackle As a remote MCP server
claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcpAnzctr As a remote MCP server
claude mcp add --transport http anzctr https://gateway.pipeworx.io/anzctr/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Only Hackle has
active-user-seriesanalytics-chart-detailanalytics-chart-listdata-report-detaildata-report-listexperiment-detailexperiment-listin-app-message-detailin-app-message-listpush-message-detailpush-message-listremote-config-create
Show the remaining 7
remote-config-detailremote-config-listremote-config-updateremote-config-update-descriptionremote-config-update-user-identifier-criteriaretention-seriesstickiness-series
Only Anzctr has
ai_visibility_checkanzctr_trialarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchclassify_rowcompany_factscompany_register_searchcompare_entities
Show the remaining 31
deep_researchdiscover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadprediction_calibrationrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribevalidate_claim
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Anzctr as of 2026-10-25). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only Hackle asks for
API_KEY (secret)
Only Anzctr asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Hackle · What it can do: Anzctr · 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.