Ext Ops Panel
Open dashboard
Comparison

Dappier vs Statiko — Telegram trends & channel analytics

Dappier is an MCP server published by DappierAI. Marketplaces we read that list it: 1 (Docker MCP Catalog). Statiko — Telegram trends & channel analytics is an MCP server published by statiko.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceDappierStatiko — Telegram trends & channel analytics
Docker MCP Catalog Listed
Version: sha256:ba9b2d17fc77
Forks (GitHub): 16
Pulls (Docker Hub): 17 566
Stars (Docker Hub): 2
Stars (GitHub): 44
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
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

Dappier vs Statiko — Telegram trends & channel analytics
FactDappierStatiko — Telegram trends & channel analytics
Marketplaces that list it11
Stars (GitHub) (differs)44No figure on GitHub
Pulls (Docker Hub) (differs)17 566No figure on Docker Hub
Forks (GitHub) (differs)16No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/dappier)Remote server (mcp.statiko.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/dappierai/dappier-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 15 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

Dappier

In its own words, on Docker MCP Catalog:

Enable fast, free real-time web search and access premium data from trusted media brands—news, financial markets, sports, entertainment, weather, and more. Build powerful AI agents with Dappier.

Statiko — Telegram trends & channel analytics

In its own words, on Official MCP Registry:

Live Telegram data: trending topics, channel profiles & metrics, post history incl. edits/deletions.

How to run each

Dappier As a local MCP server: Docker image

Claude Code
claude mcp add --env "DAPPIER_API_KEY=<YOUR_DAPPIER_API_KEY>" --transport stdio dappier -- docker run -i --rm -e DAPPIER_API_KEY mcp/dappier

Requires: DAPPIER_API_KEY (secret)

Statiko — Telegram trends & channel analytics As a remote MCP server

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

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

Only Statiko — Telegram trends & channel analytics has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Statiko — Telegram trends & channel analytics publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Statiko — Telegram trends & channel analytics publish no settings it asks for, so we do not compare settings.

What it can do: Dappier · What it can do: Statiko — Telegram trends & channel analytics · 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