Token Diet vs GenPark Context Window Token Pruner
Token Diet is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). GenPark Context Window Token Pruner is an MCP server published by alphaparkinc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  GenPark Context Window Token Pruner | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 7 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 | Token Diet | GenPark Context Window Token Pruner |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 7 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (token-diet-mcp.vercel.app/api/mcp) | On your machine (https://github.com/Alpha-Park/genpark-context-window-token-pruner-skill/releases/download/v1.0.1/genpark-context-window-token-pruner-skill-v1.0.1.mcpb) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/alphaparkinc/genpark-context-window-token-pruner-skill |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
| Endpoint at the last check (differs) | Answered with HTTP 402 (5 days 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
Token Diet
LLM token optimization gateway implementing semantic pruning.
GenPark Context Window Token Pruner
Priority-weighted context window token pruner and FIFO eviction engine protecting LLM prompt boundar
How to run each
Token Diet As a remote MCP server
claude mcp add --transport sse token-diet https://token-diet-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
GenPark Context Window Token Pruner
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Token Diet 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: Token Diet · What it can do: GenPark Context Window Token Pruner · 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.