Markitdown vs NodeProxy Web Surface Markdown Parser
Markitdown is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). NodeProxy Web Surface Markdown Parser is an MCP server published by pgalyen1987. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  NodeProxy Web Surface Markdown Parser |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cb5f26d30b6 Forks (GitHub): 14 152 Pulls (Docker Hub): 159 212 Stars (Docker Hub): 5 Stars (GitHub): 190 427 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.2 Downloads/month (PyPI): 59 Downloads/week (PyPI): 15 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
| Fact | Markitdown | NodeProxy Web Surface Markdown Parser |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 190 427 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 159 212 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 14 152 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/markitdown) | Remote server (nodeproxy-production.up.railway.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/microsoft/markitdown | github.com/pgalyen1987/nodeproxy |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 29 h ago |
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.
NodeProxy Web Surface Markdown Parser
x402 MCP web parser: URLs to Markdown for agents. USDC on Base, Polygon, Arbitrum, Ethereum.
How to run each
Markitdown As a local MCP server: Docker image
claude mcp add --transport stdio markitdown -- docker run -i --rm mcp/markitdownNodeProxy Web Surface Markdown Parser As a remote MCP server
claude mcp add --transport http nodeproxy https://nodeproxy-production.up.railway.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only NodeProxy Web Surface Markdown Parser has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of NodeProxy Web Surface Markdown Parser 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: NodeProxy Web Surface Markdown Parser · 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.