Ext Ops Panel
Open dashboard
Comparison

html-to-markdown vs DOMStrip

html-to-markdown is a plugin bundle for AI coding tools published by Kreuzberg, Inc.. Marketplaces we read that list it: 1 (Community GitHub marketplaces). DOMStrip is an MCP server published by xo0ps. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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
Marketplacehtml-to-markdownDOMStrip
Community marketplace xberg-io/html-to-markdown Listed
Version: 3.22.1
Forks (GitHub): 76
Stars (GitHub): 887
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
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

html-to-markdown vs DOMStrip
Facthtml-to-markdownDOMStrip
Marketplaces that list it11
Stars (GitHub) (differs)887 (better)0 (worse)
Forks (GitHub) (differs)76 (better)0 (worse)
Last release (differs)2026-11-13 (better)2026-11-04 (worse)
Where it runs (differs)Installs as a plugin bundleOn your machine (domstrip-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/xberg-io/html-to-markdowngithub.com/xo0ps/domstrip-client
Changes in the last 7 days (differs)30
First seen (differs)2026-11-112026-11-03

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

html-to-markdown

In its own words, on Community GitHub marketplaces:

Fast, lossless HTML→Markdown conversion with structured metadata, tables, and document-structure extraction.

DOMStrip

In its own words, on Official MCP Registry:

Turn any web page or raw HTML into compact, clean Markdown for AI agents.

How to run each

html-to-markdown As a Claude Code plugin

Claude Code
/plugin marketplace add xberg-io/html-to-markdown
/plugin install html-to-markdown@html-to-markdown

DOMStrip As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DOMSTRIP_MCP_API_KEY=<YOUR_DOMSTRIP_MCP_API_KEY>" --env "DOMSTRIP_MCP_SERVICE_ORIGIN=<YOUR_DOMSTRIP_MCP_SERVICE_ORIGIN>" --transport stdio domstrip-mcp -- uvx domstrip-mcp

Requires: DOMSTRIP_MCP_API_KEY (secret), DOMSTRIP_MCP_SERVICE_ORIGIN

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of html-to-markdown publish no settings it asks for, so we do not compare settings.

What it can do: html-to-markdown · What it can do: DOMStrip · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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