Ext Ops Panel
Open dashboard
Comparison

Markitdown vs io.github.jmshinhwa/image-host-transfer-lint

Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.jmshinhwa/image-host-transfer-lint is an MCP server published by jmshinhwa. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceMarkitdownio.github.jmshinhwa/image-host-transfer-lint
Docker MCP Catalog Listed
Version: sha256:9cb5f26d30b6
Forks (GitHub): 14 293
Pulls (Docker Hub): 163 366
Stars (Docker Hub): 5
Stars (GitHub): 191 727
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (npm): 1 175
Downloads/week (npm): 46
Forks (GitHub): 1
Stars (GitHub): 1
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

Markitdown vs io.github.jmshinhwa/image-host-transfer-lint
FactMarkitdownio.github.jmshinhwa/image-host-transfer-lint
Marketplaces that list it11
Stars (GitHub) (differs)191 727 (better)1 (worse)
Pulls (Docker Hub) (differs)163 366No figure on Docker Hub
Forks (GitHub) (differs)14 293 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/markitdown)On your machine (@readystack/image-host-transfer-lint)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/markitdowngithub.com/jmshinhwa/readystack-themes
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

Markitdown

In its own words, on Docker MCP Catalog:

A lightweight MCP server for calling MarkItDown.

io.github.jmshinhwa/image-host-transfer-lint

In its own words, on Official MCP Registry:

Names every image, font, badge and embed in your docs that sends an EU reader's IP outside the EEA

How to run each

Markitdown As a local MCP server: Docker image

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

io.github.jmshinhwa/image-host-transfer-lint As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio image-host-transfer-lint -- npx -y @readystack/image-host-transfer-lint --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 io.github.jmshinhwa/image-host-transfer-lint 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: Markitdown · What it can do: io.github.jmshinhwa/image-host-transfer-lint · 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