96 tasks · Claude Opus 4.7 · 100% · zero losses

The only MCP server
that turns Claude into
a perfect coder.

100% on 96 real coding tasks. Plain Claude scores 78.3%. With Token Savior, the same model on the same tasks lands every single one — 25 wins, 65 ties, 0 losses. Active tokens drop 77%. Wall time drops 76%. No other MCP code-navigation server has cleared this benchmark.

Pick the two agents to compare
Aplain agent
Read · Grep · Bash
vs
B+ token savior
+ 59 structural MCP tools
—
faster wall time
—
fewer active tokens
—
higher accuracy
—
losses · 96 tasks
the scorecard · what the numbers say

Same model. Same tasks.
One of them kept winning.

Two agents, one codebase, ninety prompts pulled from real engineering work — find callers, audit cycles, estimate blast radius, summarize modules. We counted tokens, wall time and correctness.

agent a · plain
Read, Grep, Bash.
no structural tools
active tokens—
wall time—
accuracy—
score—
vs
—vs—
accuracy i
——i—
agent b · token savior
Plus the graph.
+ 59 structural MCP tools (lean profile)
active tokens—
wall time—
accuracy—
score—

Accuracy, by category

avg score out of 2 · red = plain · green = token savior

Where the gap opens

context ingested per category · lower is better
−99 %
Import cycle detection
Plain agent ran 35 Bash, 20 Read calls, 113k chars, 132s. Token Savior: two MCP calls, 200 chars, 17s. Same correct answer.
0 → 2
File dependency recovery
Baseline read the whole file and missed three imports. One get_file_dependencies() call got a perfect 2/2.
21
Impossible without
Tasks the plain agent scored 0 on but Token Savior solved — community detection, hotspot audits, semantic duplicates. Amber tiles below.
the matchup · task by task

Every task.
Side by side.

Every task from the benchmark. Pick any base model on the left, any Token-Savior-wired model on the right. The numbers recompute live. Token Savior wins or ties on every single one. Click a row to jump the replay below.

#↕ category↕ task↕ A↕ B↕ Δ tokens↕ Δ wall↕ Δ chars↕ outcome↕
the graph · what Token Savior sees

A codebase isn't a folder.
It's a graph.

What you see below is the tsbench fixture parsed into its call graph: 206 symbols (functions, classes, methods, constants), 412 call edges connecting them, clustered by module. The plain agent walks this one grep at a time; Token Savior queries it directly. Drag to orbit, hover a point for details.

function class method const 206 symbols 412 call edges drag · scroll · hover
the replay · watch a task resolve

Don't take our word for it.
Watch both agents work.

Every tile is a real task from the benchmark, colored by outcome. Click one and we'll replay both agents' actual traces side by side — real tools, real timings, real answers.

Token Savior wins (—) impossible without TS (—) tie (—) losses (—)
TASK-026 Detect import cycles in the project. Any circular dependencies? If yes, list them.
wall time i
plain—
→
ts—
—
active tokens i
plain—
→
ts—
—
context chars i
plain—
→
ts—
—
score i
plain—
→
ts—
—
agent a · plain
Read · Grep · Bash
agent b · token savior
+ structural MCP
◆  works with your stack  ◆

One MCP server.
Every coding agent.

Token Savior speaks the standard Model Context Protocol. Drop it into any client, keep your tools, ship a sharper agent.

Claude Code Cursor Codex CLI Antigravity Cline Continue Windsurf Aider Gemini CLI Copilot CLI Zed any MCP client
via the open Model Context Protocol · drop-in hooks for Codex · Cursor · Gemini

Stop guessing.
Give your agent the map.

Token Savior is an open MCP server. Point it at your repo, wire it into Claude Code, Cursor, Codex, Antigravity, Cline, Continue, Windsurf, Aider, Gemini CLI — any MCP-compatible client. Ship a better agent this afternoon.

get token savior ↗ replay the benchmark