Token Optimizer (ooples) MCP Server
@ooples/token-optimizer-mcp
npm
v6.0.2
Source verified
Published by ooples — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Intelligent context window optimization for Claude Code - store content externally via caching and compression, freeing up your context window for what matters
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 6 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 15
high Dynamic code execution in server code (dist/tools/code-analysis/smart-security.js)MTC-SRC-001
In the server's implementation (`dist/tools/code-analysis/smart-security.js:190`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: , name: 'Unsafe eval()', category: 'unsafe-eval', severity: 'critical', pattern: /\beval
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/code-analysis/smart-security.js
high Shell/command execution in server code (cli-wrapper.mjs)MTC-SRC-002
In the server's implementation (`cli-wrapper.mjs:17`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { fileURLToPath } from 'url'; import { dirname, join } from 'path'; impor
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server cli-wrapper.mjs
high Shell/command execution in server code (dist/server/daemon.js)MTC-SRC-002
In the server's implementation (`dist/server/daemon.js:24`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { fileURLToPath } from 'url'; const DAEMON_VERSION = '1.0.0'; const PLATF
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/server/daemon.js
high Shell/command execution in server code (dist/tools/build-systems/run-node-bin.js)MTC-SRC-002
In the server's implementation (`dist/tools/build-systems/run-node-bin.js:21`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn, } from 'child_process'; import { existsSync, readFileSync } from 'fs'; import { join, dirname, resolve }
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/build-systems/run-node-bin.js
high Shell/command execution in server code (dist/tools/build-systems/smart-docker.js)MTC-SRC-002
In the server's implementation (`dist/tools/build-systems/smart-docker.js:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { CacheEngine } from '../../core/cache-engine.js'; import { createHash }
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/build-systems/smart-docker.js
high Shell/command execution in server code (dist/tools/build-systems/smart-network.js)MTC-SRC-002
In the server's implementation (`dist/tools/build-systems/smart-network.js:11`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { assertSafeArg } from '../../utils/safe-exec.js'; import { CacheEngine }
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/build-systems/smart-network.js
high Shell/command execution in server code (dist/tools/build-systems/smart-system-metrics.js)MTC-SRC-002
In the server's implementation (`dist/tools/build-systems/smart-system-metrics.js:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { assertSafePathArg } from '../../utils/safe-exec.js'; import { parseWind
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/build-systems/smart-system-metrics.js
high Shell/command execution in server code (dist/tools/system-operations/smart-process.js)MTC-SRC-002
In the server's implementation (`dist/tools/system-operations/smart-process.js:14`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { execFileSafe, assertSafeArg } from '../../utils/safe-exec.js'; import {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/system-operations/smart-process.js
high Shell/command execution in server code (dist/utils/safe-exec.js)MTC-SRC-002
In the server's implementation (`dist/utils/safe-exec.js:21`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: FileSync, spawn } from 'child_process'; import { promisify } from 'util'; const execFileAsyncImpl = promisify(execFile);
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/utils/safe-exec.js
high Shell/command execution in server code (hooks-core/doctor.mjs)MTC-SRC-002
In the server's implementation (`hooks-core/doctor.mjs:21`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ync, spawn } from 'node:child_process'; import { randomBytes } from 'node:crypto'; import { existsSync, statSync, readFi
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server hooks-core/doctor.mjs
high Shell/command execution in server code (integrations/cline/hooks/token-optimizer/lib/doctor.mjs)MTC-SRC-002
In the server's implementation (`integrations/cline/hooks/token-optimizer/lib/doctor.mjs:23`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ync, spawn } from 'node:child_process'; import { randomBytes } from 'node:crypto'; import { existsSync, statSync, readFi
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server integrations/cline/hooks/token-optimizer/lib/doctor.mjs
medium Dynamic module load from a non-literal (dist/tools/advanced-caching/smart-cache.js)MTC-SRC-005
In the server's implementation (`dist/tools/advanced-caching/smart-cache.js:132`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: data = await this.import(options); break; default: throw n
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/advanced-caching/smart-cache.js
medium Dynamic module load from a non-literal (dist/tools/code-analysis/smart-imports.js)MTC-SRC-005
In the server's implementation (`dist/tools/code-analysis/smart-imports.js:391`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: dImports.length} unused import(s) from '${imp.module}': ${imp.unusedImports.join(', ')}`, suggestion
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/code-analysis/smart-imports.js
medium Dynamic module load from a non-literal (dist/tools/intelligence/hooks-core-loader.js)MTC-SRC-005
In the server's implementation (`dist/tools/intelligence/hooks-core-loader.js:163`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { return (await import(bundled)); } catch (bundledError) { const fallback = fallbackDir();
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/intelligence/hooks-core-loader.js
low Package runs install-time scripts (postinstall)MTC-SUP-010
"@ooples/token-optimizer-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node scripts/postinstall.cjs
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @ooples/token-optimizer-mcp
Tools 11
Each tool and what it can reach — statically extracted from the published source.
analyze_optimizationno sensitive capabilityanalyze_project_tokensno sensitive capabilityclear_cacheno sensitive capabilitycompress_textno sensitive capabilitycount_tokensno sensitive capabilitydecompress_textno sensitive capabilityget_cache_statsno sensitive capabilityget_cachedno sensitive capabilityget_session_statsno sensitive capabilityoptimize_sessionno sensitive capability
Show 1 more tool ↓
optimize_textno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 10
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v6.0.2 latest |
A 93/100 | 15 | 1.13.0 | 2026-09-07 |
v6.0.0 |
A 93/100 | 14 | 1.13.0 | 2026-08-28 |
v5.7.0 |
A 93/100 | 14 | 1.13.0 | 2026-08-27 |
v5.6.1 |
A 93/100 | 14 | 1.12.1 | 2026-08-10 |
v5.4.3 |
A 93/100 | 14 | 1.12.1 | 2026-08-07 |
Show 5 more versions ↓
v5.3.6 |
A 93/100 | 14 | 1.12.1 | 2026-08-05 |
v5.3.5 |
A 93/100 | 14 | 1.12.1 | 2026-08-04 |
v5.3.4 |
A 93/100 | 14 | 1.12.1 | 2026-08-02 |
v5.3.2 |
A 93/100 | 14 | 1.12.1 | 2026-08-01 |
v5.2.0 |
A 93/100 | 14 | 1.12.1 | 2026-07-31 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @ooples/token-optimizer-mcp --onlineOther implementations of Token Optimizer 4
Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →
MCP server that cuts LLM token costs: accurate token counting, cost estimates across GPT/Claude/Gemini, rule-based prompt slimming with measured savings, and cheapest-model recommendations. Works with Claude, Cursor, and any MCP client.
High-performance MCP server for minimizing LLM token usage and API costs via structural code analysis and precision chunking
Orchestration + observability + coach layer for Claude Code token optimization. Measures tool usage, enforces budgets, advises on complementary tools (serena, RTK), and proactively surfaces savings tips.
Intelligent context window optimization for Claude Code - store content externally via caching and compression, freeing up your context window for what matters
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.