time-tracker vs contextburn
time-tracker is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
time-tracker is a plugin bundle for AI coding tools published by Antonis Panos. No marketplace we read lists it any more. contextburn is an MCP server published by arsentev.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-04. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  contextburn | |
|---|---|---|
| Community marketplace antonispanos/claude-mods | Removed on 2026-10-15 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 Downloads/month (PyPI): 431 Downloads/week (PyPI): 37 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | time-trackerno longer listed · | contextburn |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (contextburn) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/antonispanos/claude-mods | github.com/arsentev-ai/contextburn |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of time-tracker
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Two skills for analyzing your Claude history. token-doctor diagnoses where your Claude Code + Cowork spend goes, including sub-agent fan-out and model mix. task-profile mines…
-
OpenTelemetry and OpenInference telemetry pipeline for Claude Code sessions: documentation effectiveness, agent performance, tool usage, and cost metrics
-
Automatically tracks your Claude Code sessions, tool calls, edited files, and active time. Stores everything locally in SQLite — no cloud, no telemetry. Adds 9 MCP tools so Claude…
-
See your Claude Usage. And in what Projects, how many of your tokens are used.
-
OpenTelemetry observability for Claude Code sessions. Captures tool calls, LLM invocations, token usage, and errors as OTel traces. Send telemetry to Dash0 or any…
-
Local usage board for Claude Code. A hooks module records one metadata row per turn (exact engine cost, tokens by model, tool calls, agent spawns, context fill, rate-limit…
What each says it does
time-tracker
Tracks how long Claude was active: turns, model generation, tool runs and subagents.
contextburn
Run efficiency for coding agents: share of paid tokens that became output, not context re-reading.
How to run each
time-tracker
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
contextburn As a local MCP server: PyPI package
claude mcp add --transport stdio contextburn -- uvx contextburn mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: time-tracker · What it can do: contextburn · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.