io.github.mdfifty50-boop/token-lens

MCPcommunity
v0.1.2io.github.mdfifty50-boopUnknownUpdated 5mo agonpmGitHub

Context window token analysis and budget management

MCP server for analyzing and optimizing context window token usage. MCP tool definitions consume 40-72% of context windows before any user work begins — this server helps you measure, compress, and eliminate that waste. Analyze the token cost of your MCP tool definitions. Estimates tokens per tool using chars/4 approximation on the full JSON definition. Returns: Per-tool token cost (sorted by…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.mdfifty50-boop
LicenseUnknown
Version0.1.2
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface16 tools · 1 privileged
Security scan✓ Cleanv0.1.2 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

16 tools · 1 privileged
Statically extracted from the published packagev0.1.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

read_fileNo description published

This tool published no description. Forge does not invent one.

web_searchNo description published

This tool published no description. Forge does not invent one.

write_fileprivilegedNo description published

This tool published no description. Forge does not invent one.

git_commitNo description published

This tool published no description. Forge does not invent one.

send_emailNo description published

This tool published no description. Forge does not invent one.

big_toolNo description published

This tool published no description. Forge does not invent one.

small_toolNo description published

This tool published no description. Forge does not invent one.

health_checkNo description published

This tool published no description. Forge does not invent one.

audit_context_budgetNo description published

This tool published no description. Forge does not invent one.

optimize_tool_loadingNo description published

This tool published no description. Forge does not invent one.

compress_schemaNo description published

This tool published no description. Forge does not invent one.

analyze_session_usageNo description published

This tool published no description. Forge does not invent one.

suggest_removalsNo description published

This tool published no description. Forge does not invent one.

get_optimization_reportNo description published

This tool published no description. Forge does not invent one.

tool_aNo description published

This tool published no description. Forge does not invent one.

tool_bNo description published

This tool published no description. Forge does not invent one.

0 of 16 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for analyzing and optimizing context window token usage. MCP tool definitions consume 40-72% of context windows before any user work begins — this server helps you measure, compress, and eliminate that waste. Analyze the token cost of your MCP tool definitions. Estimates tokens per tool using chars/4 approximation on the full JSON definition. Returns: Per-tool token cost (sorted by cost), total tokens, percentage of 128K/200K/1M context windows. Given a task description, recommend…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.