Ext Ops Panel
Open dashboard
Comparison

Slack (Archived) vs reapx fediverse - Mastodon posts and instance timelines

Slack (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). reapx fediverse - Mastodon posts and instance timelines is an MCP server published by reapx.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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)reapx fediverse - Mastodon posts and instance timelines
Docker MCP Catalog Listed
Version: sha256:4cc10c3f4bd9
Forks (GitHub): 11 793
Pulls (Docker Hub): 312 710
Stars (Docker Hub): 25
Stars (GitHub): 91 324
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed, marked deprecated
Version: 1.0.0
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 reapx fediverse - Mastodon posts and instance timelines
FactSlack (Archived)reapx fediverse - Mastodon posts and instance timelines
Marketplaces that list it11
Stars (GitHub) (differs)91 324No figure on GitHub
Pulls (Docker Hub) (differs)312 710No figure on Docker Hub
Forks (GitHub) (differs)11 793No 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 checkResponded 8 h ago, requires a key

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.

reapx fediverse - Mastodon posts and instance timelines

In its own words, on Official MCP Registry:

Scrape Mastodon posts, profiles, hashtags and instance timelines across the fediverse. Pay per row.

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)

reapx fediverse - Mastodon posts and instance timelines

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 reapx fediverse - Mastodon posts and instance timelines has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of reapx fediverse - Mastodon posts and instance timelines publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of reapx fediverse - Mastodon posts and instance timelines publish no settings it asks for, so we do not compare settings.

What it can do: Slack (Archived) · What it can do: reapx fediverse - Mastodon posts and instance timelines · 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