Ext Ops Panel
Open dashboard
Comparison

Hackle vs ViralQuery

Hackle is an MCP server published by hackle-io. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). ViralQuery is an MCP server published by tfcbot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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

Where each is published
MarketplaceHackleViralQuery
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 3
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 2.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:b45e8e1c6390
Forks (GitHub): 3
Pulls (Docker Hub): 16 359
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

Hackle vs ViralQuery
FactHackleViralQuery
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)3 (better)0 (worse)
Pulls (Docker Hub) (differs)16 359No figure on Docker Hub
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineRemote server (viralquery.com/mcp)
Transport (differs)Streamable HTTP, stdioStreamable HTTP
Tools it declares (differs)19Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/hackle-io/hackle-mcpgithub.com/tfcbot/viralquery-skills
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-22Responded 6 days 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

In its own words, on Official MCP Registry:

Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.

ViralQuery

In its own words, on Official MCP Registry:

Protected research briefs, bounded scrolls, and private video feeds for agents.

How to run each

Hackle As a remote MCP server

Claude Code
claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcp

ViralQuery As a remote MCP server

Claude Code
claude mcp add --transport http viralquery https://viralquery.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of ViralQuery responded at the last daily check. How we check endpoints

Tools each declares

The marketplaces of ViralQuery publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of ViralQuery publish no settings it asks for, so we do not compare settings.

What it can do: Hackle · What it can do: ViralQuery · 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.

Where the data comes from: how the catalog is built