time-tracker vs Opik
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. Opik is an MCP server published by comet-ml. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (MCP servers)). As of our marketplace pass on 2026-10-29. 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 |  Opik | |
|---|---|---|
| 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: 3.0.8 Downloads/month (PyPI): 3 591 Downloads/week (PyPI): 814 Forks (GitHub): 37 Stars (GitHub): 225 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:0e0d7d33d5eb Forks (GitHub): 37 Pulls (Docker Hub): 17 268 Stars (Docker Hub): 1 Stars (GitHub): 225 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 3.0.8 Downloads/month (PyPI): 3 591 Downloads/week (PyPI): 814 Forks (GitHub): 37 Stars (GitHub): 225 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 · | Opik |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 0 | 225 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 17 268 |
| Forks (GitHub) (differs) | 0 | 37 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 13 |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/antonispanos/claude-mods | github.com/comet-ml/opik-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 10 h ago, requires a key |
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…
-
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.
-
Per-turn token, cost, and cache analytics for Claude Code sessions. Multi-format export (text/JSON/CSV/MD/HTML) with session blocks, weekly roll-up, subagent attribution…
-
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.
Opik
Read and score Opik traces, experiments, datasets and prompts from your AI assistant.
How to run each
time-tracker
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Opik As a remote MCP server
claude mcp add --transport http opik-mcp https://www.comet.com/opik/api/v1/mcpRequires: OPIK_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Opik has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of time-tracker publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of time-tracker publish no settings it asks for, so we do not compare settings.
What it can do: time-tracker · What it can do: Opik · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.