io.github.theluckystrike/time-tracker
MCPB · TIME-TRACKER.MCPB · SCANNED SEP 21
Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Superseded by the word-rich registry name for this server at v0.21.0; the v0.1.1 bundle this row points at is three weeks and twenty releases old.
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. How we score → Why this is hard to score →
Supply Chain Security23
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 96 of 97 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 96 of 97 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1316 tokens (~94/item across 14 items; 13 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · time-tracker.mcpb
Download bundleEvery change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Sept 26 48
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.1.1/time-tracker.mcpb@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
entry_add Add time entry ~259
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | ISO 8601 start time, e.g. 2026-09-02T09:00:00 |
| tags | array | – | Optional tags |
| task | string | – | What the work was |
No output schema declared.
No examples provided.
entry_delete Delete time entry ~27
Delete one time entry by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Entry id from entry_list |
No output schema declared.
No examples provided.
entry_edit Edit time entry ~144
Change fields of an existing entry. Only the fields you pass are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | – |
| currency | string | – | Currency of the rate, e.g. EUR |
| end | string | – | ISO 8601 |
| id | string | yes | 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 | – | – |
No output schema declared.
No examples provided.
entry_list List time entries ~91
List logged time entries (timesheet rows) as a compact table, with hours, billable flag and project. Free tier shows the last 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
export_csv Export entries to CSV ~107
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. Free tier exports the last 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO date/time lower bound |
| path | string | – | Target file path; defaults to a file in the local data directory |
| project | string | – | Optional project filter |
| to | string | – | ISO date/time upper bound |
No output schema declared.
No examples provided.
invoice_summary Invoice summary ~98
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).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | ISO date/time start of the billing period |
| project | string | yes | Project or client to invoice |
| to | string | yes | ISO date/time end of the billing period |
No output schema declared.
No examples provided.
license_activate Activate license ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~23
Show whether this server runs in free or Pro mode and where to upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_set_rate Set project rate ~101
Set the hourly rate and currency used to turn tracked hours into money for a project or client.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency: a code (EUR, USD, GBP, PLN) or a word ('euros', 'pounds', 'zl'). Default USD. |
| hourly_rate | – | yes | Hourly rate: a number (85) or the words the user said ('90 euros an hour') |
| project | string | yes | Project or client name |
No output schema declared.
No examples provided.
report Time report ~137
Timesheet report: total tracked hours and billable money for a period, grouped by (group by) project, day, task or tag - hours per project, how much to bill. Money is grouped by currency and never mixes EUR with USD. Free tier covers the last 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | table (default), json or csv |
| from | string | yes | ISO date/time start of the period |
| group_by | string | yes | project | day | task | tag (tag is Pro) |
| project | string | – | Optional project filter |
| to | string | yes | ISO date/time end of the period |
No output schema declared.
No examples provided.
timer_start Start timer ~201
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. Accepts an hourly rate and a currency, e.g. rate '90 euros'.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency of the rate: EUR, USD, GBP, PLN, or words like 'euros'. Defaults to the project currency, else USD. |
| project | string | yes | 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 ('90 euros an hour'). Defaults to the project rate. |
| tags | array | – | Free-form tags, e.g. ['dev','meeting'] |
| task | string | – | What you are working on right now |
No output schema declared.
No examples provided.
timer_status Timer status ~27
Show the running timer, how long it has been running, and today's total hours so far.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timer_stop Stop timer ~41
Stop the running timer and log it as a time entry. Returns the duration and the entry id.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional note stored with the entry |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/time-tracker MCP server?
io.github.theluckystrike/time-tracker is an MCP server listed in the public MCP registry as io.github.theluckystrike/time-tracker. 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.1.1/time-tracker.mcpb).
Is the io.github.theluckystrike/time-tracker MCP server safe to use?
io.github.theluckystrike/time-tracker scores 57 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-tracker MCP server expose?
io.github.theluckystrike/time-tracker exposes 13 tools: license_status, license_activate, timer_start, timer_stop, timer_status, and 8 more. Their descriptions and schemas cost roughly 1,298 tokens of context every time the server is loaded.
Is the io.github.theluckystrike/time-tracker MCP server still maintained?
io.github.theluckystrike/time-tracker is marked deprecated in the MCP registry. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.theluckystrike/time-tracker MCP server under?
io.github.theluckystrike/time-tracker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.