TokenSaver
NUGET · TOKENSAVER.MCP · SCANNED SEP 20
Structural warm start for AI coding agents in .NET: cheap Roslyn signature maps of C#/.NET files.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 86 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1270 tokens (~423/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the TokenSaver MCP server?
TokenSaver runs locally as a NuGet package, launched with dnx TokenSaver.Mcp@1.15.5 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · TokenSaver.Mcp
claude mcp add byggarepop-tokensaver -- dnx TokenSaver.Mcp@1.15.5 --yes
{
"mcpServers": {
"byggarepop-tokensaver": {
"command": "dnx",
"args": [
"TokenSaver.Mcp@1.15.5",
"--yes"
]
}
}
} {
"servers": {
"byggarepop-tokensaver": {
"command": "dnx",
"args": [
"TokenSaver.Mcp@1.15.5",
"--yes"
]
}
}
} codex mcp add byggarepop-tokensaver -- dnx TokenSaver.Mcp@1.15.5 --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"byggarepop-tokensaver": {
"type": "local",
"command": [
"dnx",
"TokenSaver.Mcp@1.15.5",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
byggarepop-tokensaver:
command: "dnx"
args: ["TokenSaver.Mcp@1.15.5", "--yes"] {
"McpServers": {
"byggarepop-tokensaver": {
"Transport": "stdio",
"Command": "dnx",
"Arguments": [
"TokenSaver.Mcp@1.15.5",
"--yes"
]
}
}
} {
"mcpServers": {
"byggarepop-tokensaver": {
"command": "dnx",
"args": [
"TokenSaver.Mcp@1.15.5",
"--yes"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −2
- Stability: pass → 0.83 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 0
- Stability: 0.97 → pass security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed nuget/TokenSaver.Mcp@1.15.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unreadable |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
minify_file ~227
Read a whole file of a supported type COMPACTLY: auto-detects the format from the file extension and strips comments + collapses whitespace losslessly (logic unchanged). Best for non-C# files — JavaScript/TypeScript, Python, HTML, CSS/SCSS/LESS, JSON/JSONC, YAML, XML/.NET project files (.csproj, .props, .targets, .config, .resx), C/C++, X++, and VB.NET. For a C# file prefer outline_c_sharp_file (skeleton) — it saves far more; use MinifyFile on C# only when you genuinely need the whole file. Indent-sensitive formats (Python, YAML) preserve leading indentation. Do NOT call on files under 50 lines — the tool-call overhead exceeds the savings; use the Read tool instead. After calling on a C# file, do NOT re-Read it whole — Read only the lines you need (offset+limit).
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute path to a source file. Language is detected by extension. |
No output schema declared.
No examples provided.
outline_c_sharp_file ~186
CALL THIS FIRST before reading or editing any C#/VB file over ~50 lines: returns a skeleton — every type and member as a signature with its source line range (e.g. `public Task Foo(); // L31-44`), NO method/property bodies. Typically 70-95% smaller than the file. Ideal for 'what's in this file?' and 'where would I add X?'. Then Read ONLY the line-range you need (Read with offset+limit) — never re-read the whole file. Much cheaper than MinifyFile for discovery. Supports .cs, .razor.cs, .razor, and .vb. Do NOT call on files under ~50 lines — just Read them.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute path to a .cs, .razor.cs, .razor, or .vb file. |
No output schema declared.
No examples provided.
trace_di_registrations ~209
Finds every Dependency-Injection registration across a project that references a named type (interface OR concrete), answering 'where is IFoo wired, and to what implementation?' — the question a constructor caller-trace CANNOT answer because DI-constructed types are never created with 'new'. Returns a compact table: file:line, registration method, ServiceType -> ImplType, lifetime, and keyed key. Detects Add/TryAdd{Scoped,Singleton,Transient}, AddKeyed*, in generic, typeof(), and factory-lambda forms. Pass the project root or .csproj path; obj/ and bin/ are excluded. Syntactic name matching. C# only.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | yes | Absolute path to a project folder or .csproj file. All .cs files under it (excluding obj/ and bin/) are scanned. |
| typeName | string | yes | The service or implementation type name to find registrations for (simple name, e.g. 'IFoo'). |
No output schema declared.
No examples provided.
What is the TokenSaver MCP server?
TokenSaver is an MCP server listed in the public MCP registry as io.github.Byggarepop/tokensaver. Structural warm start for AI coding agents in .NET: cheap Roslyn signature maps of C#/.NET files. This page covers its NuGet package (TokenSaver.Mcp).
Is the TokenSaver MCP server safe to use?
TokenSaver scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TokenSaver MCP server expose?
TokenSaver exposes 3 tools: minify_file, trace_di_registrations, outline_c_sharp_file. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.
Is the TokenSaver MCP server still maintained?
TokenSaver is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TokenSaver MCP server under?
TokenSaver declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.