token-inspector vs io.github.ooples/token-optimizer-mcp
token-inspector is a plugin bundle for AI coding tools published by msiShariful. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.ooples/token-optimizer-mcp is an MCP server published by ooples. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  token-inspector |  io.github.ooples/token-optimizer-mcp |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.2.0 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 7.5.1 Downloads/month (npm): 11 452 Downloads/week (npm): 4 428 Forks (GitHub): 68 Stars (GitHub): 549 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | token-inspector | io.github.ooples/token-optimizer-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (worse) | 549 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 68 (better) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@ooples/token-optimizer-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/msishariful/claude-token-inspector | github.com/ooples/token-optimizer-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
token-inspector
Two skills that help you understand and optimize your Claude Code context window. Inspect Context gives you a full token breakdown by source (files, history, skills, MCP configs) with a keep/remove recommendation for each. Find Bloat scans everything loaded and surfaces what's burning tokens without contributing to your current task — with exact commands to remove it.
io.github.ooples/token-optimizer-mcp
Context-window optimization: caching, compression & smart file tools that cut tokens 60-90%.
How to run each
token-inspector As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install token-inspector@claude-communityio.github.ooples/token-optimizer-mcp As a local MCP server: npm package
claude mcp add --transport stdio token-optimizer-mcp -- npx -y @ooples/token-optimizer-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of token-inspector publish no settings it asks for, so we do not compare settings.
What it can do: token-inspector · What it can do: io.github.ooples/token-optimizer-mcp · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.