Ext Ops Panel
Open dashboard
Comparison

Slack (Archived) vs Hacker News Scraper: Stories, Comments & Users

Slack (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Hacker News Scraper: Stories, Comments & Users is an MCP server published by ranovam.com. 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
MarketplaceSlack (Archived)Hacker News Scraper: Stories, Comments & Users
Docker MCP Catalog Listed
Version: sha256:4cc10c3f4bd9
Forks (GitHub): 11 868
Pulls (Docker Hub): 313 599
Stars (Docker Hub): 25
Stars (GitHub): 91 555
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
No figure published
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

Slack (Archived) vs Hacker News Scraper: Stories, Comments & Users
FactSlack (Archived)Hacker News Scraper: Stories, Comments & Users
Marketplaces that list it11
Stars (GitHub) (differs)91 555No figure on GitHub
Pulls (Docker Hub) (differs)313 599No figure on Docker Hub
Forks (GitHub) (differs)11 868No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/slack)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)8Not published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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

Slack (Archived)

In its own words, on Docker MCP Catalog:

Interact with Slack Workspaces over the Slack API.

Hacker News Scraper: Stories, Comments & Users

In its own words, on Official MCP Registry:

Scrape Hacker News stories, comments and user profiles as clean JSON with points, author…

How to run each

Slack (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "SLACK_BOT_TOKEN=<YOUR_SLACK_BOT_TOKEN>" --transport stdio slack -- docker run -i --rm -e SLACK_BOT_TOKEN mcp/slack

Requires: SLACK_BOT_TOKEN (secret)

Hacker News Scraper: Stories, Comments & Users

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: Authorization header

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

Only Hacker News Scraper: Stories, Comments & Users has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Hacker News Scraper: Stories, Comments & Users publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Hacker News Scraper: Stories, Comments & Users publish no settings it asks for, so we do not compare settings.

What it can do: Slack (Archived) · What it can do: Hacker News Scraper: Stories, Comments & Users · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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