Ext Ops Panel
Open dashboard
Comparison

Markdownify vs dev.averra/extract

Markdownify is an MCP server published by zcaceres. Marketplaces we read that list it: 1 (Docker MCP Catalog). dev.averra/extract is an MCP server published by averra.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceMarkdownifydev.averra/extract
Docker MCP Catalog Listed
Version: sha256:afa1ab8e1563
Forks (GitHub): 254
Pulls (Docker Hub): 72 417
Stars (Docker Hub): 2
Stars (GitHub): 3 001
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
Downloads/month (npm): 363
Downloads/week (npm): 80
Forks (GitHub): 0
Stars (GitHub): 0
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

Markdownify vs dev.averra/extract
FactMarkdownifydev.averra/extract
Marketplaces that list it11
Stars (GitHub) (differs)3 001 (better)0 (worse)
Pulls (Docker Hub) (differs)72 417No figure on Docker Hub
Forks (GitHub) (differs)254 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/markdownify)On your machine (@averra/extract-mcp)
Transportstdiostdio
Tools it declares (differs)11Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/zcaceres/markdownify-mcpgithub.com/swwyymm/averra-extract-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Markdownify

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for converting almost anything to Markdown.

dev.averra/extract

In its own words, on Official MCP Registry:

URL-to-Markdown API for AI pipelines — clean markdown with metadata and caching.

How to run each

Markdownify As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio markdownify -- docker run -i --rm mcp/markdownify

dev.averra/extract As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio extract -- npx -y @averra/extract-mcp

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

Tools each declares

The marketplaces of dev.averra/extract publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Markdownify · What it can do: dev.averra/extract · 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