io.github.DataLeadsPRO/url-to-markdown vs io.github.vojtisprime11/web-fetcher
io.github.DataLeadsPRO/url-to-markdown is an MCP server published by DataLeadsPRO. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vojtisprime11/web-fetcher is an MCP server published by vojtisprime11. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  io.github.DataLeadsPRO/url-to-markdown |  io.github.vojtisprime11/web-fetcher |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (npm): 125 Downloads/week (npm): 51 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 | io.github.DataLeadsPRO/url-to-markdown | io.github.vojtisprime11/web-fetcher |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (data.dataleads.pro/mcp/url-to-markdown) | On your machine (mcp-server-web-fetcher) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dataleadspro/url-to-markdown | github.com/vojtisprime11/mcp-server-web-fetcher |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 18 h ago | no remote endpoint we check |
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
io.github.DataLeadsPRO/url-to-markdown
Convert any webpage to clean LLM-ready markdown, extraction-first, with article and news modes.
io.github.vojtisprime11/web-fetcher
Turns any web page into clean Markdown, page metadata and classified links for LLMs.
How to run each
io.github.DataLeadsPRO/url-to-markdown As a remote MCP server
claude mcp add --transport http url-to-markdown https://data.dataleads.pro/mcp/url-to-markdownio.github.vojtisprime11/web-fetcher As a local MCP server: npm package
claude mcp add --transport stdio web-fetcher -- npx -y mcp-server-web-fetcherCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.DataLeadsPRO/url-to-markdown has a remote endpoint we check. How we check endpoints
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 io.github.DataLeadsPRO/url-to-markdown publish no settings it asks for, so we do not compare settings.
What it can do: io.github.DataLeadsPRO/url-to-markdown · What it can do: io.github.vojtisprime11/web-fetcher · Compare two other plugins
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.