Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
TokenSafe is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Cut AI coding agent token usage up to 90% via AST slicing, dependency graphs & security guards.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user tokensafe-mcp '--' npx -y tokensafe mcp
# 2 — ask your agent for something these tools do
# smart_read_file, get_architecture_graph, get_api_surface and 9 more
TokenSafe costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts TokenSafe as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user tokensafe-mcp '--' npx -y tokensafe mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Reads a code file using AST skeletonization and predictive dependency prefetching to save up to 90% context tokens.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Absolute path to the code file |
| symbol | string | no | Optional: targeted function or class name for graph-guided skeletonization |
| include_deps | boolean | no | Optional: whether to include 1-hop dependencies in full (default: true). Set false for single-symbol surgical isolation. |
| start_line | integer | no | Optional: starting line number |
| end_line | integer | no | Optional: ending line number |
Returns top architectural God Nodes and dependency topology for the target project. Call this BEFORE reading files or searching.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_path | string | no | Absolute root path of the project directory. Highly recommended to pass explicitly. |
Generates and returns a compact markdown map of all exported interfaces, classes, and types in the project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_path | string | no | Absolute root path of the project directory. Highly recommended to pass explicitly. |
Compresses a verbose developer prompt into an ultra-dense TOCP S-Expression via DeepSeek-V3 / Regex.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | Natural language request from developer |
Context Budget HUD: estimates how much of the model's context window this session has consumed (tools/history/prompts breakdown, 50/80/95% thresholds). Call when deciding whether to compact or start fresh.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | string | no | Optional: model name to resolve window size (default: env TOKENSAFE_CONTEXT_WINDOW or 200k) |
| window_tokens | integer | no | Optional: explicit context window size in tokens |
| session_id | string | no | Optional: session identifier (default: mcp_session) |
On-demand context compaction: folds a long agent conversation transcript into a compact Consolidated State Ledger. Use when the context window feels heavy or before starting a new subtask inside the same session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transcript_path | string | yes | Path to the JSONL transcript of the current session |
| invocation_num | integer | no | Optional: current turn number (default 3; folding requires >= 3 turns) |
Per-stage shell command rewrites: prunes lockfiles, caps unbounded git log/show/blame/rg
| Parameter | Type | Required | Notes |
|---|---|---|---|
| command | string | yes | Raw bash command line |
Slices unified diffs, omitting lockfiles and minimizing context lines to reduce tokens by up to 80%.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| diff | string | yes | Raw git diff text |
| max_context | integer | no | Maximum surrounding context lines (default: 2) |
Returns cumulative token and cost savings analytics.
No parameter schema on file.
Pre-flight security & hygiene audit for commands or code snippets. Detects secret leaks, SQL injection, TLS bypass (incl. git-level), CORS wildcard, destructive commands, raw grep, and never-terminating streams (tail -f, watch, docker attach).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| command | string | no | Optional: Terminal command line to audit |
| code | string | no | Optional: Code snippet, replacement diff, or file content to audit |
| file_path | string | no | Optional: File path being written or modified |
Returns a clean, token-efficient directory tree up to depth N without permissions, timestamps, or ignored folders (node_modules, .git, dist, .env). Replaces verbose ls -la.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Path to the directory (relative to project root or absolute) |
| depth | integer | no | Maximum traversal depth (default: 2, max: 4) |
| max_entries | integer | no | Maximum entries to display before pruning (default: 80) |
Safe, token-bounded symbol and text search across the codebase. Replaces raw grep/find with clean, line-numbered markdown matches (-90% tokens).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Text, identifier, or symbol name to search for |
| scope | string | no | Scope of search: 'code' (source files only), 'config' (json, toml, yaml), or 'all' (default: 'all') |
| path | string | no | Directory or project path to search (alias for project_path) |
| project_path | string | no | Optional root directory path (defaults to current project) |
| max_results | integer | no | Maximum matching lines to return (default: 25, max: 100) |
| case_sensitive | boolean | no | Whether search is case-sensitive (default: false) |
| use_regex | boolean | no | Whether query is a regular expression (default: false) |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install TokenSafe or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.2.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish TokenSafe can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.