# io.github.theluckystrike/time-tracker-timesheet-billable-hours (remote · mcp.zovo.one)

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

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-time-tracker-timesheet-billable-hours/mcp-time-tracker.md), [page](https://verifymcp.io/servers/theluckystrike-time-tracker-timesheet-billable-hours/mcp-time-tracker)
- mcpb · `time-tracker.mcpb`: 47/100, [markdown](https://verifymcp.io/servers/theluckystrike-time-tracker-timesheet-billable-hours/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-time-track.md), [page](https://verifymcp.io/servers/theluckystrike-time-tracker-timesheet-billable-hours/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-time-track)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/time-tracker`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/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 2205 tokens (~137/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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

### How do I install the io.github.theluckystrike/time-tracker-timesheet-billable-ho… MCP server?

io.github.theluckystrike/time-tracker-timesheet-billable-ho… is a hosted endpoint at https://mcp.zovo.one/mcp/time-tracker, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-time-tracker-timesheet-billable-h 'https://mcp.zovo.one/mcp/time-tracker'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-time-tracker-timesheet-billable-h": {
      "url": "https://mcp.zovo.one/mcp/time-tracker"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-time-tracker-timesheet-billable-h": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/time-tracker"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-time-tracker-timesheet-billable-h]
url = "https://mcp.zovo.one/mcp/time-tracker"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-time-tracker-timesheet-billable-h": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/time-tracker",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-time-tracker-timesheet-billable-h --url 'https://mcp.zovo.one/mcp/time-tracker' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-time-tracker-timesheet-billable-h:
    url: "https://mcp.zovo.one/mcp/time-tracker"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-time-tracker-timesheet-billable-h": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/time-tracker"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-time-tracker-timesheet-billable-h -t streamable-http -u 'https://mcp.zovo.one/mcp/time-tracker'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-time-tracker-timesheet-billable-h": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/time-tracker"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-20 (score 83, +1)

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

### 2026-09-18 (score 82, +1)

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

### 2026-09-17 (score 81, 0)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (score 81, +1)

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

### 2026-09-14 (score 80, +1)

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

### 2026-09-12 (score 79, +1)

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

### 2026-09-11 (score 78, 0)

- [security] Tool “invoice_summary” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 78, +1)

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

## MCP tools (14)

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

### `timer_start` (~202 tokens)

Start timer

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.

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` (~60 tokens)

Stop timer

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.

Input parameters:

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

### `timer_status` (~49 tokens)

Timer status

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.

### `entry_add` (~252 tokens)

Add time entry

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.

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` (~109 tokens)

List time entries

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.

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` (~60 tokens)

Delete time entry

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.

Input parameters:

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

### `entry_edit` (~175 tokens)

Edit time entry

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.

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` (~182 tokens)

Invoice summary

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.

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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-time-tracker-timesheet-billable-hours/mcp-time-tracker#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 78
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 77
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36
- 2026-09-02: 36

## 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 hosted endpoint (https://mcp.zovo.one/mcp/time-tracker).

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

io.github.theluckystrike/time-tracker-timesheet-billable-ho… scores 83 out of 100 on VerifyMCP. 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,135 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/time-tracker-timesheet-billable-ho… MCP server require authentication?

Yes. io.github.theluckystrike/time-tracker-timesheet-billable-ho… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/time-tracker-timesheet-billable-ho… MCP server still maintained?

io.github.theluckystrike/time-tracker-timesheet-billable-ho… is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/time-tracker
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/time-tracker
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/time-tracker
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-time-tracker-timesheet-billable-hours/mcp-time-tracker.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-time-tracker-timesheet-billable-hours/mcp-time-tracker.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-time-tracker-timesheet-billable-hours/mcp-time-tracker