Ext Ops Panel
Open dashboard
Comparison

cache-stats vs Turbo Quant Memory

cache-stats is a plugin bundle for AI coding tools published by arafattehsin. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Turbo Quant Memory is an MCP server published by Lexus2016. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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

Where each is published
Marketplacecache-statsTurbo Quant Memory
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.31.0
Downloads/month (PyPI): 845
Downloads/week (PyPI): 61
Forks (GitHub): 1
Stars (GitHub): 9
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

cache-stats vs Turbo Quant Memory
Factcache-statsTurbo Quant Memory
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)9 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-10-14 (worse)2026-10-16 (better)
Where it runs (differs)Installs as a plugin bundleOn your machine (turbo-quant-memory)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/arafattehsin/cache-stats-extensiongithub.com/lexus2016/turbo_quant_memory
Changes in the last 7 days (differs)31
First seen2026-10-112026-10-11

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

cache-stats

In its own words, on Copilot CLI: github/awesome-copilot:

Shows live prompt-cache reuse, expiry, token composition, and AI Credit cost for the current GitHub Copilot session without making model calls.

Turbo Quant Memory

In its own words, on Official MCP Registry:

Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.

How to run each

cache-stats

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Turbo Quant Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --env "TQMEMORY_SECRETS_PASSPHRASE=<YOUR_TQMEMORY_SECRETS_PASSPHRASE>" --transport stdio turbo-quant-memory -- uvx turbo-quant-memory serve

Requires: TQMEMORY_SECRETS_PASSPHRASE (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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 cache-stats publish no settings it asks for, so we do not compare settings.

What it can do: cache-stats · What it can do: Turbo Quant Memory · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built