Markitdown vs JidoSeal
Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). JidoSeal is an MCP server published by jidoseal.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
| Marketplace |  Markitdown |  JidoSeal |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cb5f26d30b6 Forks (GitHub): 14 583 Pulls (Docker Hub): 168 857 Stars (Docker Hub): 5 Stars (GitHub): 194 048 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (PyPI): 605 Downloads/week (PyPI): 50 Forks (GitHub): 0 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
| Fact | Markitdown | JidoSeal |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 194 048 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 168 857 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 14 583 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-27 |
| Where it runs (differs) | On your machine (mcp/markitdown) | On your machine (jidoseal-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/microsoft/markitdown | github.com/jidoseal/jidoseal-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
A lightweight MCP server for calling MarkItDown.
JidoSeal
Checks a Markdown folder's OKF frontmatter tier, locally. No-egress is a vendor claim: see README.
How to run each
Markitdown As a local MCP server: Docker image
claude mcp add --transport stdio markitdown -- docker run -i --rm mcp/markitdownJidoSeal As a local MCP server: PyPI package
claude mcp add --transport stdio jidoseal-mcp -- uvx jidoseal-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of JidoSeal 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: JidoSeal · 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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.