Tokenscope
NPM · @WARTZAR-BEE/TOKENSCOPE-MCP · SCANNED AUG 3
Analyze Claude Code session cost & context attribution: output, cached re-reads, cache writes.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
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 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 536 tokens (~178/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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @wartzar-bee/tokenscope-mcp
claude mcp add wartzar-bee-tokenscope -- npx -y @wartzar-bee/tokenscope-mcp
codex mcp add wartzar-bee-tokenscope -- npx -y @wartzar-bee/tokenscope-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wartzar-bee-tokenscope": {
"type": "local",
"command": [
"npx",
"-y",
"@wartzar-bee/tokenscope-mcp"
],
"enabled": true
}
}
} openclaw mcp add wartzar-bee-tokenscope --command npx --arg -y --arg @wartzar-bee/tokenscope-mcp
mcp_servers:
wartzar-bee-tokenscope:
command: "npx"
args: ["-y", "@wartzar-bee/tokenscope-mcp"] {
"mcpServers": {
"wartzar-bee-tokenscope": {
"command": "npx",
"args": [
"-y",
"@wartzar-bee/tokenscope-mcp"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 +11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 26
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@wartzar-bee/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
analyze_claude_cost ~206
Analyze a Claude Code session's token cost and context attribution. Reads Claude Code session JSONL (read-only, local) and returns the total cost, the spend breakdown (model output vs re-sent cached context vs cache-write vs fresh input), the per-turn context-growth peak/avg, cache efficiency, cost by model, subagent spend, tool-call counts, and plain-language insights. With no path it analyzes your most recent Claude Code session under ~/.claude/projects.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | — | Aggregate ALL sessions under ~/.claude/projects (ignored if `path` is set). Default false. |
| path | string | — | Optional path to a session .jsonl file or a directory of them. Omit to use your latest Claude Code session. |
| pricing | object | — | Optional per-model price overrides, e.g. {"claude-opus-4": {"in": 15, "out": 75}} (USD per 1M tokens). |
No output schema declared.
No examples provided.
get_cost_benchmark ~224
Compare a Claude Code session against tokenscope's shipped reference set of real sessions (n=66) and report percentiles: how big the session's cost is vs the set, its re-sent-context share, and how cache-efficient it is ('more cache-efficient than ~P% of measured sessions'). Either pass a `path` to a session, or pass explicit `totalCost`/`resentPct`/`cacheEfficiency` numbers. This is a yardstick reference set, not a population census.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | — | With no path-derived metrics, aggregate ALL sessions. Default false. |
| cacheEfficiency | number | — | Cache efficiency percent (0-100). Used if `path` is omitted. |
| path | string | — | Optional session .jsonl path/dir to derive the metrics from. |
| resentPct | number | — | Percent of spend that was re-sent (cached) context. Used if `path` is omitted. |
| totalCost | number | — | Session total cost (USD). Used if `path` is omitted. |
No output schema declared.
No examples provided.
tokenscope_share_summary ~106
Produce a privacy-safe, shareable summary of a Claude Code session built ONLY from aggregate numbers (no file paths, no prompt/response content) — safe to paste in public. Returns both a structured summary object and a ready-to-paste markdown block. With no path it uses your latest session.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | — | Aggregate ALL sessions. Default false. |
| path | string | — | Optional session .jsonl path/dir. Omit to use your latest session. |
No output schema declared.
No examples provided.