Skip to main content
Glama

Related Servers

Alternatives to tarelab

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      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
      26 PyPI
      MIT
    • A
      license
      A
      quality
      B
      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
    • A
      license
      Not graded
      quality
      C
      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.
      44 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Reads the Claude Code, Codex and OpenCode usage logs already on your machine and reports token totals, per-day and per-hour activity, a per-agent and per-model breakdown, and a year-in-review recap. It makes no network request at all — a test fails if any source file in the package can open a socket.
      4
      14
      MIT

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool targets a distinct analysis layer: aggregate spend summary (tare_wrapped), per-commit cost comparison (tare_receipt), and per-session cache diagnostics (tare_cache). There is some thematic overlap since all report cost/context metrics, but the descriptions make the boundaries clear enough to select correctly.

    Naming Consistency5/5

    All three tools follow the exact same pattern: 'tare_' prefix plus a single lowercase noun (wrapped, receipt, cache), all in snake_case. No deviation whatsoever.

    Tool Count4/5

    Three tools is on the low end but appropriate for a focused cost-analytics server; each covers a genuinely different view (overall, per-commit, per-session). It earns its place, though one could imagine a fourth for session listing or trend history.

    Completeness4/5

    The surface covers the core analytics: spend overview, before/after fix comparison, and cache cost projection. Minor gaps exist—no way to list sessions or agents, filter by time range, or drill into individual fixes—but agents can work around these for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues