Skip to main content
Glama
iyashjayesh

tokenchit

by iyashjayesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tokenchit

No user-submitted related servers found.

    Related Servers

    • claudeusage

      syk8015
      A
      license
      A
      quality
      C
      maintenance
      Analyzes local Claude Code logs to measure subscription value, waste, and rate-limit usage, including chat share and current limits, without uploading data.
      4
      MIT

    • tokenscope

      wartzar-bee
      A
      license
      Not graded
      quality
      B
      maintenance
      Analyzes Claude Code session token usage and cost locally — where spend actually lands across cache-read, cache-write and output, and what is consuming the context window. Read-only and offline: it parses your own session files and exposes analyze_claude_cost, get_cost_benchmark and tokenscope_share_summary.
      113 npm
      4
      MIT

    • contextburn

      arsentev-ai
      A
      license
      B
      quality
      C
      maintenance
      Lets a coding agent inspect its own run efficiency mid-session from local Claude Code transcripts, exposing the share of paid tokens that became model output versus context re-reading. Ships two stdio tools — one returning the shares as structured data and one returning the full cost-weighted report — with no network calls.
      2
      28 PyPI
      MIT

    • claude-spend

      mpalermiti
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides tools for Claude to query local Claude Code token usage and cost data, enabling spend analysis and insights through natural language.
      19 npm
      1
      MIT

    This server cannot be deployed

    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation4/5

    get_usage (windowed totals), get_daily_usage (per-day series), and get_recap (year-in-review aggregates) have partially overlapping subject matter, but each description clearly states its scope and output shape. detect_agents is cleanly distinct. Minor risk that an agent asks for a time range and picks get_usage over get_daily_usage.

    Naming Consistency4/5

    Three tools follow a clean get_<noun> snake_case pattern (get_usage, get_daily_usage, get_recap). detect_agents breaks the prefix convention slightly but is still snake_case and readable, so the set is nearly uniform.

    Tool Count4/5

    Four focused tools cover the analytics surface without redundancy. It is on the lean side but each tool earns its place; nothing feels padded or missing at the count level.

    Completeness4/5

    Covers lifetime/window totals, daily series, yearly recap, and agent discovery/diagnostics, which addresses the core questions of a usage-tracking server. Possible gaps like per-project rollups or cross-agent comparison views are not indicated as supported, but no obvious dead end for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources