npm:token-lens-mcp

Item: npm:token-lens-mcp
Rating: 55
Author: wmcp.sh

https://www.npmjs.com/package/token-lens-mcp

55/100 · MCP Trust Grade · checked 2h ago · MCP 0.1.2

What it offers — 7 tools · Developer Tools

health_check

Returns server health, uptime, version, and storage stats

audit_context_budget

Analyze the token cost of MCP tool definitions. Estimates tokens per tool using chars/4 on the full JSON definition. Returns per-tool costs and percen

optimize_tool_loading

Given a task description, recommend the minimal set of tools needed. Uses keyword matching and category relevance scoring to rank tools.

compress_schema

Compress a verbose tool schema to reduce token usage. Light: remove short descriptions. Medium: shorten descriptions, remove examples. Aggressive: str

analyze_session_usage

Track which tools are actually called vs loaded in a session. Register tools, log calls, and generate waste reports showing unused tools ranked by tok

suggest_removals

Identify tools that can be removed based on usage history. Scores: never_used > not_used_30_days > rarely_used. Returns removal candidates with estima

get_optimization_report

Full context window health check combining audit, removal suggestions, and compression recommendations. Returns an executive summary with health grade

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 7 tool(s) detected in source

Security (OWASP MCP)30%15

⚠ prompt-injection / hidden-instruction markup in source
uses eval/exec/child_process (review for unsanitized input)
scanned 4 source files

Maintenance / popularity20%92

published within 90 days
3 published versions

Tool hygiene15%70

no TypeScript types
4 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
27 weekly downloads

Findings

FAILMCP01 Prompt-injection / hidden-instruction markup found in package source.

INFO Static analysis of npm package token-lens-mcp@0.1.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:token-lens-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:token-lens-mcp grade F

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Atoken-lens-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade F](https://wmcp.sh/mcp/grade/npm%3Atoken-lens-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Atoken-lens-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Atoken-lens-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Atoken-lens-mcp/badge.svg" alt="MCP Trust Grade F · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.