Tallybook
Related Servers
Alternatives to Tallybook
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first dashboard + MCP server that parses Claude Code and Codex JSONL files into a SQLite cost / token tracker. Per-MCP and per-tool breakdown, session drill-down, dedup by request_id; never talks to vendor APIs51001MIT
- AlicenseNot gradedqualityAmaintenanceEnables local-first tracking of AI token usage and costs from Claude Code and OpenCode, answering queries about tokens, models, sessions, and cost through MCP tools and a CLI, with no network calls.1611MIT
- AlicenseBqualityFmaintenanceTrack LLM token costs across Claude, GPT and Gemini. MCP server + CLI with optimization hints and $ savings estimates.851MIT
- AlicenseAqualityBmaintenanceEnables analyzing coding-agent session transcripts to measure tool efficiency, detect loops, track test outcomes, and report costs, with MCP tools for listing sessions, analyzing sessions, finding loops, and generating cost reports.4MIT
- AlicenseBqualityAmaintenanceLets 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.2MIT
- AlicenseAqualityBmaintenanceToken-cost telemetry for OpenClaw, queryable from Claude or any MCP-aware agent. Provides per-agent and per-provider cost attribution, anomaly detection, model-routing recommendations, and 30-day forecasts.7MIT
TDQS
Scored across 8 tools
Most tools target distinct facets: report (aggregate), sessions (list), session (single), agents (sub-agent breakdown), changes (model-change points), finding (one finding), prices, refresh. The main risk is report vs sessions vs agents overlapping in cost-summary territory, and session vs sessions differing only by plural, but descriptions clearly separate them.
All names are single lowercase nouns (agents, changes, finding, prices, refresh, report, session, sessions), so the convention is applied consistently. The only weakness is session/sessions and agents/sessions reading similarly, which slightly hurts predictability.
Eight tools is well-scoped for a cost-tracking server, with each tool mapping to a clear function (scan, price table, aggregate report, listing, drill-down, sub-agent detail, model-change tracking, findings). Nothing appears redundant or padded.
The surface covers the full lifecycle: refresh to ingest data, prices for computation basis, report/sessions/agents for aggregate and sub-agent views, session for turn-level drill-down, changes for model change comparisons, and finding for full advice with evidence. No obvious gaps or dead ends for the stated purpose.