io.github.DataLeadsPRO/website-to-json vs io.github.j0hanz/superfetch
io.github.DataLeadsPRO/website-to-json is an MCP server published by DataLeadsPRO. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.j0hanz/superfetch is an MCP server published by j0hanz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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/website-to-json |  io.github.j0hanz/superfetch |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.2 Downloads/month (npm): 194 Downloads/week (npm): 35 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/website-to-json | io.github.j0hanz/superfetch |
|---|---|---|
| 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/website-to-json) | On your machine (@j0hanz/superfetch) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dataleadspro/website-to-json | github.com/j0hanz/super-fetch-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 25 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/website-to-json
Turn any webpage into structured JSON with CSS-selector schemas - strings select text, attributes
io.github.j0hanz/superfetch
Intelligent web content fetcher MCP server that converts HTML to clean, AI-readable JSONL format
How to run each
io.github.DataLeadsPRO/website-to-json As a remote MCP server
claude mcp add --transport http website-to-json https://data.dataleads.pro/mcp/website-to-jsonio.github.j0hanz/superfetch As a local MCP server: npm package
claude mcp add --transport stdio superfetch -- npx -y @j0hanz/superfetchCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.DataLeadsPRO/website-to-json 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
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.DataLeadsPRO/website-to-json · What it can do: io.github.j0hanz/superfetch · 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.