Token Optimizer MCP server
io.github.omkar9854/token_optimizer·v0.1.0·1 starsReversible context compression for AI agents: cut token usage up to 94%, originals retrievable
1 stars18 downloads/wk
Reviews
Write oneNobody has reviewed Token Optimizer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Token Optimizer tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- Code scan12 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 68 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Token Optimizer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 18
- more than 5% of 12,191 servers with a package
Install Token Optimizer in Claude Code, Cursor or VS Code
claude mcp add token_optimizer -- uvx slimctx
What the publisher says
From the Token Optimizer repository's README, as published. We do not edit it. Read it on GitHub
slimctx — the token optimizer for AI agents
<!-- mcp-name: io.github.omkar9854/token_optimizer -->
Zero-dependency, fully-reversible context compression for AI agents.
slimctx compresses what your agent reads — tool outputs, logs, JSON, source files, prose — before it reaches the LLM. Same answers, fraction of the tokens. Pure Python stdlib: no ML models, no downloads, no network calls, ever. Auditable end to end in ~1,600 lines.
Live output of python3 benchmarks/demo.py — run it yourself, nothing is staged.
from slimctx import Pipeline, Config
pipe = Pipeline(Config(target_tokens=32_000))
result = pipe.compress(messages) # OpenAI/Anthropic-style dicts
print(result.savings_ratio) # e.g. 0.82
original = pipe.retrieve("a1b2c3d4...") # byte-exact original, any timeResults (synthetic workloads modeled on real agent traffic)
Every run also verifies that each planted "needle" (the FIXME, the OOMKill, the outlier) survives compression, and that every lossy transform is byte-exact reversible. Reproduce with python3 benchmarks/bench.py.
How it works
messages ──► ContentRouter ──► one of:
├─ JSON : lossless tabularization (repeated keys → header,
│ constant columns → legend), then relevance-ranked
│ row selection only if still over budget
├─ LOG : Drain-style template mining — repeated lines
│ collapse to `pattern [x1432]`; errors verbatim
├─ CODE : AST skeleton — signatures + docstrings kept,
│ bodies elided EXCEPT those relevant to the query
└─ TEXT : extractive sentence selection (BM25 + salience
+ position), verbatim, never paraphrasedThe four guarantees
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Token Optimizer: common questions
- Is Token Optimizer MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Token Optimizer safety report
- How do I install Token Optimizer?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Token Optimizer need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Token Optimizer maintained?
- The last commit was 107 days ago (2026-07-19). The latest release is v0.1.0.
- How does Token Optimizer compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers); downloads a week 18 (more than 5% of 12,191 servers with a package). Full comparison.