Token Savior runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 10 Aug 2026.
Structural codebase MCP server with persistent memory: navigate by symbol, recall across sessions.
What the code does
We read the source, 3 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
[path.join(HOOKS_DIR, script), ...args],
return subprocess.run(
f"https://api.telegram.org/bot{token}/sendMessage", data=data
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Token Savior
same job, measured the same wayPersistent codebase intelligence that gives AI assistants memory across sessions
Persistent codebase intelligence that gives AI assistants memory across sessions
Cross-vendor semantic memory: recall across Claude Code / Codex / Grok sessions by meaning.
Local memory for Claude Code. Semantic recall across session history with zero API calls.
Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.
Persistent memory for Claude Code. Search, recall, and re-inject context from any session.
Persistent memory for Claude Code. Search, recall, and re-inject context from any session.
Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot.
Token Savior — questions
Answers built from our own checks of this server.