MCP server for Compresh — production-grade context compression with TUL 2.0 query-aware retrieval (paid tier) over the open tulbase core
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"compresh-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# compresh-mcp **MCP server for Compresh** — production-grade context compression for LLM agent conversations. > Compresh adds **query-aware retrieval (TUL 2.0)** on top of the open-source > [`tulbase`](https://github.com/compresh/tulbase) compression core. Instead of > summarizing older turns, it retrieves the turns relevant to the current > question — lossless and role-tagged — from the full conversation history. > This is the **paid tier** distribution, and it works free without an account > (local tulbase compression). ## Architecture (0.3.0+) - **Local**: bundled `tulbase` (MIT, vendored as `compresh_mcp.tulbase`) runs on every turn for fast compression + cold-storage support (`fetch_compressed` / `list_compressed` MCP tools). Works with **no API key and no account** — fully local, free. - **Server**: the **TUL 2.0** paid layer (query-aware retrieval over full history, role-preserving render) runs on Compresh infrastructure via the `/v1/tul2` endpoint, gated by your Compresh API key + tier. - **Degraded mode**: if `/v1/tul2` is unreachable (or your trial/credit runs out), compresh-mcp transparently falls back to the local tulbase result so compression never blocks. The paid endpoint was the legacy `/v1/tul1` through 0.2.x; 0.3.0 calls the canonical `/v1/tul2` (the TUL 1.0 Q-matrix layer was retired in the 15 Jun 2026 retrieval pivot). The server keeps `/v1/tul1` as a deprecated alias, so older clients keep working. Previously (0.1.0, yanked), paid classifiers shipped inside the client package and leaked paid features locally — install 0.3.0 or later. See [CHANGELOG.md](./CHANGELOG.md). ## What's the difference vs `tulbase-mcp`? Both ship the same open-source compression core (cleanup, TurnBox, modality elision to cold storage, Protection Zone, LexRank summarization). `tulbase-mcp` is currently GitHub-only (not yet on PyPI). The difference is what happens on top of the shared core: | Feature | `tulbase-mcp` (free, open-source) | `compresh-mcp` (paid) | …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.