session-tracker vs Hackle
session-tracker is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
session-tracker is a plugin bundle for AI coding tools published by Aguinaldo Tupy. No marketplace we read lists it any more. Hackle is an MCP server published by hackle-io. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-23. 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 | ||
|---|---|---|
| Community marketplace aguinaldotupy/claude-session-tracker | Removed on 2026-10-17 Version: 4.1.1 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:b45e8e1c6390 Forks (GitHub): 3 Pulls (Docker Hub): 16 261 Stars (Docker Hub): 0 Stars (GitHub): 3 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 | session-trackerno longer listed · | Hackle |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 2 | 3 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 16 261 |
| Forks (GitHub) (differs) | 0 | 3 |
| Last release | Not published | Not published |
| 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 | 19 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 8 | Not published |
| Parts of the bundle (differs) | 19 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/aguinaldotupy/claude-session-tracker | github.com/hackle-io/hackle-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-22 |
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 session-tracker
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
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…
-
Monitor Claude Code's 5-hour session token usage from the system tray (Anthropic's own percentage plus this PC's count), and reopen sessions a crash killed
-
Search, inspect, replay, and manage Claude Code sessions tracked by the Agent Monitor dashboard — find sessions by project, model, status, or date; reconstruct event timelines…
-
Real-time session logging, command history, and auto-naming for Claude Code
-
Generate an explorable HTML report of Claude Code session usage — tokens, cache efficiency, subagents, skills, and the most expensive prompts — from local ~/.claude/projects…
-
Query Claude Code session history, tool calls, hooks, and token usage through a DuckDB index over local transcripts
What each says it does
session-tracker
Track Claude Code session duration with automatic timestamps, elapsed time skill, and optional status line integration
Hackle
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
How to run each
session-tracker
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Hackle As a remote MCP server
claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hackle has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of session-tracker publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of session-tracker publish no settings it asks for, so we do not compare settings.
What it can do: session-tracker · What it can do: Hackle · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.