# io.github.theluckystrike/time-tracking (mcpb · time-tracker.mcpb)

Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.

- Trust score: 52/100 (low)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- mcpb · `time-tracker.mcpb`: 52/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-time-tracking/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-time-track.md), [page](https://verifymcp.io/servers/theluckystrike-time-tracking/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-time-track)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/time-tracker.mcpb`
- Version: `0.21.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1962 tokens (~130/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "entry_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/time-tracker.mcpb`

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 51, +4)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-12 (score 47)

First indexed and scored.

## MCP tools (14)

### `license_status` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

### `timer_start` (~194 tokens)

Start timer

Start a stopwatch for billable work on a project or client (timesheet / hours per project). Only one timer runs at a time: starting a new one stops and logs the previous one.

Input parameters:

- `currency` (string): Currency of the rate: EUR, USD, GBP, PLN, or words like 'euros'. Defaults to the project currency, else USD.
- `project` (string, required): Project or client name, e.g. 'acme-website'. A partial name that matches exactly one existing project is used as that project.
- `rate`: Hourly rate for this timer only; a number (90) or the words the user said, e.g. rate '90 euros an hour'. Defaults to the project rate set by project_set_rate.
- `tags` (array): Free-form tags, e.g. ['dev','meeting']
- `task` (string): What you are working on right now

### `timer_stop` (~41 tokens)

Stop timer

Stop the running timer and log it as a time entry. Returns the duration and the entry id.

Input parameters:

- `note` (string): Optional note stored with the entry

### `timer_status` (~27 tokens)

Timer status

Show the running timer, how long it has been running, and today's total hours so far.

### `entry_add` (~259 tokens)

Add time entry

Log billable (or non-billable) time you already worked on a project - a timesheet entry. Give start plus either end or minutes, and optionally the hourly rate and its currency, e.g. rate '90 euros an hour' -> EUR.

Input parameters:

- `billable` (boolean): Default true; set false for non-billable work
- `currency` (string): Currency of the rate: EUR, USD, GBP, PLN, or words like 'euros'. Defaults to the project currency, else USD.
- `end` (string): ISO 8601 end time (or use minutes)
- `minutes` (number): Duration in minutes (alternative to end)
- `note` (string): Optional note
- `project` (string, required): Project or client name. A partial name that matches exactly one existing project is used as that project.
- `rate`: Hourly rate for this entry; a number (90) or the words the user said ('90 euros an hour')
- `start` (string, required): ISO 8601 start time, e.g. 2026-09-02T09:00:00
- `tags` (array): Optional tags
- `task` (string): What the work was

### `entry_list` (~91 tokens)

List time entries

List logged time entries (timesheet rows) as a compact table, with hours, billable flag and project. Free tier shows the last 7 days.

Input parameters:

- `from` (string): ISO date/time lower bound
- `limit` (integer): Maximum rows, newest first (default 50)
- `project` (string): Filter by project name
- `to` (string): ISO date/time upper bound

### `entry_delete` (~27 tokens)

Delete time entry

Delete one time entry by id.

Input parameters:

- `id` (string, required): Entry id from entry_list

### `entry_edit` (~144 tokens)

Edit time entry

Change fields of an existing entry. Only the fields you pass are changed.

Input parameters:

- `billable` (boolean)
- `currency` (string): Currency of the rate, e.g. EUR
- `end` (string): ISO 8601
- `id` (string, required): Entry id from entry_list
- `minutes` (number): New duration in minutes, keeps start
- `note` (string)
- `project` (string)
- `rate`: Hourly rate override for this entry, a number or words like '90 euros'
- `start` (string): ISO 8601
- `tags` (array)
- `task` (string)

### `project_set_rate` (~283 tokens)

Set project rate

Set the hourly rate and currency used to turn tracked hours into money for a project or client. Returns the new rate and, when re-rating is asked for, how many already logged entries changed.

Input parameters:

- `apply_to_existing` (boolean): Re-rate time already logged for this project: every entry is re-stamped with the new rate, including entries that already carry one. Default false: the new rate applies to future entries only, becaus…
- `currency` (string): Currency: a code (EUR, USD, GBP, PLN) or a word ('euros', 'pounds', 'zl'). Defaults to the shared business profile's default_currency, else USD.
- `hourly_rate` (required): Hourly rate: a number (85) or the words the user said ('90 euros an hour'). '1,200 USD' is 1200; '12,50 EUR' is 12.50; anything ambiguous is refused.
- `only_missing` (boolean): Only meaningful with apply_to_existing. True restores the old fill-the-gaps behaviour: only entries that carry no rate of their own are touched. Default false, which re-stamps every entry of the proj…
- `project` (string, required): Project or client name. A partial name that matches exactly one existing project is used as that project.

### `report` (~263 tokens)

Time report

Timesheet report: total tracked hours and billable money for a period, optionally grouped by (group by) project, day, task or tag - hours per project, how much to bill. Omit group_by for the plain total per currency.

Input parameters:

- `format` (string): table (default), json or csv. Every format carries one amount per currency, never a mixed-currency sum.
- `from` (string, required): ISO date/time start of the period. On the free tier the window is clamped to the last 7 days; Pro reports over the full history.
- `group_by` (string): project | day | task | tag. Optional: omit it for the plain total per currency, with no breakdown. Money is grouped by currency and EUR is never added to USD.
- `project` (string): Optional project filter
- `to` (string, required): ISO date/time end of the period. On the free tier the window is clamped to the last 7 days; Pro reports over the full history.
- `unbilled_only` (boolean): Default true: hours already put on an invoice (entry_mark_billed) are excluded, so the report answers 'what is still to bill'. Pass false for the full timesheet including invoiced work.

### `export_csv` (~170 tokens)

Export entries to CSV

Call this tool to export the timesheet to a CSV file (excel-friendly) you can hand to a bookkeeper: one row per entry with hours, billable, rate, currency and amount. Returns the file path written.

Input parameters:

- `from` (string): ISO date/time lower bound. On the free tier the export is clamped to the last 7 days; Pro exports the full history.
- `path` (string): Target file path; a relative path resolves against the working directory. Defaults to a timestamped file in the local data directory, and the full path is returned.
- `project` (string): Optional project filter
- `to` (string): ISO date/time upper bound. On the free tier the export is clamped to the last 7 days; Pro exports the full history.

### `entry_mark_billed` (~199 tokens)

Mark time entries as billed

Close the loop after an invoice is issued: stamp the tracked hours that went on it with the invoice number, so report and invoice_summary stop offering them and the same hours are never billed twice.

Input parameters:

- `billed_at` (string): ISO timestamp of the stamp, defaults to now
- `from` (string): ISO date/time start of the billed period, used with project
- `ids` (array): Exact entry ids, normally the entry_ids invoice_summary returned. Pass either ids or project plus from and to. Entries already billed are left alone and listed back to you.
- `invoice_number` (string, required): The invoice these hours were put on, e.g. INV-2026-0001
- `project` (string): Project or client, used with from and to instead of ids; every billable entry in that range is stamped.
- `to` (string): ISO date/time end of the billed period, used with project

### `invoice_summary` (~181 tokens)

Invoice summary

Turn tracked billable time into invoice line items for one project or client: hours, hourly rate, amount per task and the total, in the currency the work was logged in (EUR 225.00, not $225.00).

Input parameters:

- `from` (string, required): ISO date/time start of the billing period. Free covers the last 7 days; Pro invoices any period from the full history.
- `project` (string, required): Project or client to invoice
- `to` (string, required): ISO date/time end of the billing period. Free covers the last 7 days; Pro invoices any period from the full history.
- `unbilled_only` (boolean): Default true: hours already put on an invoice (entry_mark_billed) are left out, so the same hours are never billed twice. Pass false to see the whole period including invoiced work.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-time-tracking/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-time-track#diagnostics

## Score history

- 2026-09-21: 52
- 2026-09-20: 51
- 2026-09-19: 51
- 2026-09-18: 47
- 2026-09-17: 47
- 2026-09-16: 47
- 2026-09-15: 47
- 2026-09-14: 47
- 2026-09-13: 47
- 2026-09-12: 47

## Common questions

### What is the io.github.theluckystrike/time-tracking MCP server?

io.github.theluckystrike/time-tracking is an MCP server listed in the public MCP registry as io.github.theluckystrike/time-tracking. Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/time-tracker.mcpb).

### Is the io.github.theluckystrike/time-tracking MCP server safe to use?

io.github.theluckystrike/time-tracking scores 52 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.theluckystrike/time-tracking MCP server expose?

io.github.theluckystrike/time-tracking exposes 14 tools: license_status, license_activate, timer_start, timer_stop, timer_status, and 9 more. Their descriptions and schemas cost roughly 1,944 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/time-tracking MCP server under?

io.github.theluckystrike/time-tracking declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/time-tracker
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-time-tracking/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-time-track.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-time-tracking/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-time-track.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-time-tracking/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-time-track