Security audit of ooples/token-optimizer-mcp · MCP Server by ooples · ★ 586
Yes — token-optimizer-mcp passed AgentSkillsHub's rule-based security scan with no dangerous patterns detected. As with any third-party skill, confirm what credentials it requests before production use.
What it is: 91.5% fewer tokens on tool output on Headroom's own benchmark, where Headroom removes 61.4%. Separately, the same SWE-bench tasks resolved at 0.71x the cost of plain Claude Code. Plus memory across sessions and subscription quota pacing. Claude Code, Codex, Copilot, Gemini and 12 more. Local, MIT.
No dangerous patterns were detected: no credential exfiltration, no obfuscated downloads, no sandbox-escape attempts, no prompt-injection markers.
| Security grade | ✓ SAFE |
| Quality score | 71/100 |
| GitHub stars | 586 |
| Language | JavaScript |
| License | MIT |
| Last updated |
Browse all MCP Server skills →
This is AgentSkillsHub's free basic audit: an automated rule-based scan with 44 published rules built on SlowMist's agent-security taxonomy (credential theft, obfuscated payloads, privilege escalation, covert instructions to the agent, and more), applied the same way to every open-source AI agent skill and MCP server we grade and refreshed every 8 hours. A SAFE grade is a scan result, not a guarantee — deep 5-dimension audits (code · credentials · vendor · supply-chain · operational) are available for enterprise. Audited: .