tarelab
Related Servers
Alternatives to tarelab
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceToken usage and estimated cost for Claude Code, Codex, Cursor and 20 more AI coding agents, read locally from their session files. No API key, no telemetry.221AGPL 3.0
- AlicenseBqualityBmaintenanceLets 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.226 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables offline, read-only forensic analysis of Claude Code session transcripts, providing exact token usage, cost estimates, context growth, and compaction suggestions.MIT
- AlicenseAqualityBmaintenanceAnalyzes local Claude Code logs to measure subscription value, waste, and rate-limit usage, including chat share and current limits, without uploading data.4MIT
- AlicenseNot gradedqualityCmaintenanceAnalyzes 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 npm4MIT
- AlicenseNot gradedqualityAmaintenanceReads 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.414MIT
TDQS
Scored across 3 tools
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.
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.
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.
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.