@v1nvn/readability vs Imperium RAG-Diet — Web & Document Context Distiller (85-97% Token Savings)
@v1nvn/readability is an MCP server published by v1nvn. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Imperium RAG-Diet — Web & Document Context Distiller (85-97% Token Savings) is an MCP server published by agentdiet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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 |  @v1nvn/readability |  Imperium RAG-Diet — Web & Document Context Distiller (85-97% Token Savings) |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.56.0 Downloads/month (npm): 4 119 Downloads/week (npm): 822 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 7.0.17 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 | @v1nvn/readability | Imperium RAG-Diet — Web & Document Context Distiller (85-97% Token Savings) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-09 (better) | 2026-10-21 (worse) |
| Where it runs (differs) | On your machine (@v1nvn/readability) | Remote server (rag-diet.agentdiet.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/v1nvn/agentic | github.com/robertoyanguas-ops/assay |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-21 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 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
@v1nvn/readability
MCP server that turns rendered (post-JS) HTML into clean Markdown + metadata via Readability, Turndown, and DOMPurify.
Imperium RAG-Diet — Web & Document Context Distiller (85-97% Token Savings)
Strips 85-97% of HTML/DOM boilerplate into clean Markdown, skeletons, or BM25-ranked RAG chunks.
How to run each
@v1nvn/readability
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Imperium RAG-Diet — Web & Document Context Distiller (85-97% Token Savings) As a remote MCP server
claude mcp add --transport http rag-diet https://rag-diet.agentdiet.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Imperium RAG-Diet — Web & Document Context Distiller (85-97% Token Savings) has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of @v1nvn/readability nor its endpoint list any 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: @v1nvn/readability · What it can do: Imperium RAG-Diet — Web & Document Context Distiller (85-97% Token Savings) · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.