Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/time-tracker-timesheet-billable-hours

MCPB · TIME-TRACKER.MCPB · 2 COMPONENTS · SCANNED SEP 20

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

47 Trust /100
Trust breakdown (7 categories)

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 96 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability84
  • 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
  • Context-footprint check failed: tool/resource definitions use about 2147 tokens (~143/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% 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 15 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

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 bundle
Changelog

Every 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.

  • 17 Sept 26 47

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/time-tracker.mcpb@0.22.0

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 Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~2,129 tokens

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 →

Tool Tokens
entry_add ~252

Log time already worked as one entry and return its id, duration and amount. Give start plus end or minutes. rate is hourly in MAJOR units and is frozen on the entry, so a later rate change never moves it.

NameTypeReqDescription
billablebooleanDefault true; set false for non-billable work
currencystringCurrency of the rate: EUR, USD, GBP, PLN, or words like 'euros'. Defaults to the project currency, else USD.
endstringISO 8601 end time (or use minutes)
minutesnumberDuration in minutes (alternative to end)
notestringOptional note
projectstringyesProject or client name. A partial name that matches exactly one existing project is used as that project.
rateHourly rate for this entry; a number (90) or the words the user said ('90 euros an hour')
startstringyesISO 8601 start time, e.g. 2026-09-02T09:00:00
tagsarrayOptional tags
taskstringWhat the work was

No output schema declared.

No examples provided.

entry_delete ~60

Delete one logged entry by id and report the project and hours removed. It never touches a running timer. A billed entry goes too, losing the invoice record, so correct one with entry_edit instead.

NameTypeReqDescription
idstringyesEntry id from entry_list

No output schema declared.

No examples provided.

entry_edit ~175

Change one logged entry by id; only the fields you pass move. minutes keeps start and moves end, an end at or before start is refused, tags REPLACES the list, and rate is hourly in MAJOR units.

NameTypeReqDescription
billableboolean
currencystringCurrency of the rate, e.g. EUR
endstringISO 8601
idstringyesEntry id from entry_list
minutesnumberNew duration in minutes, keeps start
notestring
projectstring
rateHourly rate override for this entry, a number or words like '90 euros'
startstringISO 8601
tagsarray
taskstring

No output schema declared.

No examples provided.

entry_list ~109

List logged entries as a table of id, day, start, project, task, hours, billable, tags and note, newest first, with total hours. Free reads the last 7 days and says so; Pro reads the whole history.

NameTypeReqDescription
fromstringISO date/time lower bound
limitintegerMaximum rows, newest first (default 50)
projectstringFilter by project name
tostringISO date/time upper bound

No output schema declared.

No examples provided.

entry_mark_billed ~199

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.

NameTypeReqDescription
billed_atstringISO timestamp of the stamp, defaults to now
fromstringISO date/time start of the billed period, used with project
idsarrayExact 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_numberstringyesThe invoice these hours were put on, e.g. INV-2026-0001
projectstringProject or client, used with from and to instead of ids; every billable entry in that range is stamped.
tostringISO date/time end of the billed period, used with project

No output schema declared.

No examples provided.

export_csv ~170

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.

NameTypeReqDescription
fromstringISO date/time lower bound. On the free tier the export is clamped to the last 7 days; Pro exports the full history.
pathstringTarget 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.
projectstringOptional project filter
tostringISO date/time upper bound. On the free tier the export is clamped to the last 7 days; Pro exports the full history.

No output schema declared.

No examples provided.

invoice_summary ~182

Turn tracked billable time into invoice lines for one project: hours, hourly rate, amount per task and the total, one line per rate so two rates never average. Hours already marked billed are left out. Free: last 7 days.

NameTypeReqDescription
fromstringyesISO date/time start of the billing period. Free covers the last 7 days; Pro invoices any period from the full history.
projectstringyesProject or client to invoice
tostringyesISO date/time end of the billing period. Free covers the last 7 days; Pro invoices any period from the full history.
unbilled_onlybooleanDefault 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.

No output schema declared.

No examples provided.

license_activate ~71

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

NameTypeReqDescription
keystringyesLicense key from the checkout confirmation page

No output schema declared.

No examples provided.

license_status ~54

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

project_set_rate ~283

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.

NameTypeReqDescription
apply_to_existingbooleanRe-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…
currencystringCurrency: a code (EUR, USD, GBP, PLN) or a word ('euros', 'pounds', 'zl'). Defaults to the shared business profile's default_currency, else USD.
hourly_rateyesHourly 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_missingbooleanOnly 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…
projectstringyesProject or client name. A partial name that matches exactly one existing project is used as that project.

No output schema declared.

No examples provided.

report ~263

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.

NameTypeReqDescription
formatstringtable (default), json or csv. Every format carries one amount per currency, never a mixed-currency sum.
fromstringyesISO 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_bystringproject | 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.
projectstringOptional project filter
tostringyesISO 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_onlybooleanDefault 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.

No output schema declared.

No examples provided.

timer_start ~202

Start a stopwatch for work on a project and return the start time. Only one runs at a time: a new one stops and logs the previous, naming it. rate is an hourly rate in MAJOR units for this timer only.

NameTypeReqDescription
currencystringCurrency of the rate: EUR, USD, GBP, PLN, or words like 'euros'. Defaults to the project currency, else USD.
projectstringyesProject or client name, e.g. 'acme-website'. A partial name that matches exactly one existing project is used as that project.
rateHourly 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.
tagsarrayFree-form tags, e.g. ['dev','meeting']
taskstringWhat you are working on right now

No output schema declared.

No examples provided.

timer_status ~49

Report the running timer and today's total hours. Today is the local calendar day, so a timer started at 23:30 yesterday contributes only the minutes since midnight. No arguments, and it writes nothing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

timer_stop ~60

Stop the running timer and log it as one entry. Returns the duration, the money at the rate in force and the new entry id. With no timer running it says so and writes nothing.

NameTypeReqDescription
notestringOptional note stored with the entry

No output schema declared.

No examples provided.

Common questions

What is the io.github.theluckystrike/time-tracker-timesheet-billable-ho… MCP server?

io.github.theluckystrike/time-tracker-timesheet-billable-ho… is an MCP server listed in the public MCP registry as io.github.theluckystrike/time-tracker-timesheet-billable-ho…. 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.22.0/time-tracker.mcpb).

Is the io.github.theluckystrike/time-tracker-timesheet-billable-ho… MCP server safe to use?

io.github.theluckystrike/time-tracker-timesheet-billable-ho… scores 47 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-timesheet-billable-ho… MCP server expose?

io.github.theluckystrike/time-tracker-timesheet-billable-ho… exposes 14 tools: license_status, license_activate, timer_start, timer_stop, timer_status, and 9 more. Their descriptions and schemas cost roughly 2,129 tokens of context every time the server is loaded.

What licence is the io.github.theluckystrike/time-tracker-timesheet-billable-ho… MCP server under?

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