idle-timing vs io.github.theluckystrike/time-tracking
idle-timing is a plugin bundle for AI coding tools published by clankercode. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.theluckystrike/time-tracking is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  idle-timing |  io.github.theluckystrike/time-tracking |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.4.0 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.21.1 Forks (GitHub): 0 Stars (GitHub): 2 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 | idle-timing | io.github.theluckystrike/time-tracking |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.zovo.one/mcp/time-tracking) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | Unlicense OR CC0-1.0 | Not stated |
| Repository (differs) | github.com/clankercode/claude-inject-idle-time | github.com/theluckystrike/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
idle-timing
- Injects timing block to prompts (not user-visible) covering local date-time, idle time (since agent turn ended), and prior turn execution time. - Shows `[after Xm Ys]` to user via post submit hook to indicate how long it was between that prompt and agent finishing prior turn. - Provides statusline integration for idle time.
io.github.theluckystrike/time-tracking
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
How to run each
idle-timing As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install idle-timing@claude-communityio.github.theluckystrike/time-tracking As a remote MCP server
claude mcp add --transport http time-tracking https://mcp.zovo.one/mcp/time-tracking --header "Authorization: Bearer <YOUR_TOKEN>"Requires: MCP_LICENSE_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.theluckystrike/time-tracking has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of idle-timing publish no settings it asks for, so we do not compare settings.
What it can do: idle-timing · What it can do: io.github.theluckystrike/time-tracking · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.