clocknext vs io.github.dailyaiagents-cpu/mrr-floor-check
clocknext is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
clocknext is a plugin bundle for AI coding tools published by ClockNext. No marketplace we read lists it any more. io.github.dailyaiagents-cpu/mrr-floor-check is an MCP server published by dailyaiagents-cpu. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  io.github.dailyaiagents-cpu/mrr-floor-check | |
|---|---|---|
| Community marketplace clocknext/clocknext-mcp | Removed on 2026-10-15 Version: 0.13.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 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 | clocknextno longer listed · | io.github.dailyaiagents-cpu/mrr-floor-check |
|---|---|---|
| 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 | Not stated |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/clocknext/clocknext-mcp | github.com/dailyaiagents-cpu/dailyai-os |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-13 | 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 clocknext
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
time-tracking-billing-hours io.github.theluckystrike/time-tracking-billing-hours
Billable-hours time tracking with rates and CSV export, running inside Claude or Cursor.
-
Track time, manage clients and projects, review timesheets, and create invoices with OAuth.
-
mcp io.github.ClockNext/mcp
Meter usage and manage usage-based billing from AI tools via the ClockNext API.
-
time-tracking io.github.theluckystrike/time-tracking
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
-
Toggl Track integration for Claude Code. Log time entries by project and task, query what you tracked today or this week, and get aggregated summaries — all via natural language…
-
Time tracking, live project budgets, and billing exports for service firms.
What each says it does
clocknext
Meter usage and manage usage-based billing from AI coding tools via the ClockNext API.
io.github.dailyaiagents-cpu/mrr-floor-check
Daily Stripe MRR query against a configured floor
How to run each
clocknext
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.dailyaiagents-cpu/mrr-floor-check
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands 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
The marketplaces of io.github.dailyaiagents-cpu/mrr-floor-check publish no settings it asks for, so we do not compare settings.
What it can do: clocknext · What it can do: io.github.dailyaiagents-cpu/mrr-floor-check · 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.