Token Savior MCP server
io.github.Mibayy/token-savior·v4.13.0·1.2k starsStructural codebase MCP server with persistent memory: navigate by symbol, recall across sessions.
1.2k stars
Reviews
Write oneNobody has reviewed Token Savior yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Token Savior 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-24 · same rubric, same numbers if you re-run it
- Code scan192 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 46 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Token Savior 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,157
- more than 95% of 28,688 servers
Install Token Savior in Claude Code, Cursor or VS Code
claude mcp add token-savior -- uvx token-savior-recall
What the publisher says
From the Token Savior repository's README, as published. We do not edit it. Read it on GitHub
<!-- mcp-name: io.github.Mibayy/token-savior -->
Token Savior
One MCP server. One profile. 97.9% on tsbench at -80% tokens.
Structural code navigation, persistent memory, and Bash command rewriting for AI coding agents.
-brightgreen)
mibayy.github.io/token-savior -- project site + benchmark landing Benchmark source + fixtures: not currently published (see Reproducing the score below)
Benchmark -- 96 real coding tasks (Claude Opus 4.7, May 2026)
Reproduces with the optimized profile (single env var). The harness that produced these numbers is described below; its repository is not public at the moment, so take the figures as reported rather than as independently verifiable.
A re-measurement was published here on 2026-08-09 and has been withdrawn on 2026-08-10. It reported new-token savings from a small replacement harness. Those numbers did not measure this server at all: across 143 benchmark sessions, exactly one called a Token Savior tool. The client running the harness had MCP deferred-tool loading enabled, so all 18 tools sat behind a ToolSearch lookup instead of appearing in the model's manifest. The model never saw them and fell back to Grep and Read — 66 greps, 30 reads, one MCP call. What varied between the "profiles" was the size of the cached prefix, not what the agent did.
The lesson is worth more than the numbers were: a benchmark of an MCP server must assert that its tools were actually called. Ours did not, so it happily compared two identical agents. That assertion now exists in the harness.
The headline figures above therefore stand as reported and unverified, as stated in the previous paragraph. Re-measuring them properly is open work.
Who starred this repo?
On June 30, 2026 GitHub restricted stargazer and watcher lists to repo admins and collaborators, which broke every "who starred my repo" tool at once. I rebuilt one that still works, precisely because it only reads repos you own or can push to: starscope ranks the people who starred or forked your repo by influence, and surfaces their social accounts when their GitHub profile declares them.
Numbers on this very repo, computed with it: 1,147 people, 27% with a public social account, and the most followed carries 18,922 followers. The named list is visible to the repo owner and to nobody else — the public page shows aggregates only.
What's new
Release notes live where they can't drift out of sync with the code:
- CHANGELOG.md for the full history
- Releases for the tagged builds
- PyPI for what pip will actually give you
Quick start
pip install "token-savior-recall[mcp]"Add to your MCP config (e.g. Claude Code):
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Token Savior: common questions
- Is Token Savior MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Token Savior safety report
- How do I install Token Savior?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Token Savior need an API key?
- No secret keys are declared. It reads 3 settings from the environment.
- Is Token Savior maintained?
- The last commit was 86 days ago (2026-08-10). The latest release is v4.13.0.
- What can I use instead of Token Savior?
- Servers from other publishers that do the same job: Codebase Memory MCP server, Deja Vu MCP server and Honcho MCP server. Compare all Token Savior alternatives.
- How does Token Savior compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); github stars 1,157 (more than 95% of 28,688 servers). Full comparison.
Alternatives to Token Savior
Same job from other publishers: the closest match first, then the best rated.
- Codebase MemoryCodebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.not reviewedWidely usedC
- Deja Vudeja-vu: local memory over the session histories of forty-three coding agents.not reviewedEstablishedA
- HonchoMemory that reasons: continual learning for stateful agents. Better context, fewer tokens.not reviewedEstablishedA
State Memory MCPPersistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.not reviewedEstablishedA
KnowlPersistent memory for AI agents, for code, research and everyday life. Stale facts retire.not reviewedEstablishedA
