McpStamp Time Tracker
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Track billable hours: timers, timesheets, weekly totals, CSV export, unbilled hours to invoices.
Available components
Last scanned (17 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 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 2607 tokens (~118/item across 22 items; 20 tools + 2 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 Management97
- Stability observed for 29 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
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 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
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.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 16 Oct 26 +1
- Schema quality: 137 → 113 ▲ functional
- Server version: 0.22.0 → 0.22.6 functional
- New tool “target_set” functional
- New tool “target_check” functional
- New tool “summary_week” functional
- New tool “summary_day” functional
- New tool “summary_client” functional
- New tool “entry_log” functional
- 15 Oct 26 +69
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 14 Oct 26 −69
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 10 Oct 26 0
- Stability: 0.97 → pass security
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 97. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://mcp.zovo.one/mcp/time-tracker
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/time-tracker"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/time-tracker"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/time-tracker |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/time-tracker |
| Authorisation server | https://mcp.zovo.one |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/time-tracker | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/time-tracker | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/time-tracker |
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 ~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.
| 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 ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Entry id from entry_list |
No output schema declared.
No examples provided.
entry_edit Edit time entry ~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.
| 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 ~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.
| 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.
entry_log Log work time ~103
Log work time for a client/project in one step: minutes worked plus an optional note. The entry starts now minus the minutes, so it lands on today's day and week summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Client or project name. A partial name matching exactly one project resolves to it. |
| minutes | number | yes | Minutes of work to log |
| note | string | – | Optional note |
| project | string | – | Sub-project or task label stored on the entry |
No output schema declared.
No examples provided.
entry_mark_billed Mark time entries as 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
export_csv Export entries to 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
invoice_summary 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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | ISO date/time start of the billing period. Free covers the last 7 days; Pro invoices any period from the full history. |
| project | string | yes | Project or client to invoice |
| to | string | yes | 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. |
No output schema declared.
No examples provided.
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_set_rate Set project 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | yes | 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 | yes | Project 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 Time 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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | table (default), json or csv. Every format carries one amount per currency, never a mixed-currency sum. |
| from | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
summary_client Client summary ~53
All-time totals for one client/project: hours, entry count and billable amount, with a per-day breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Client or project name. A partial name matching exactly one project resolves to it. |
No output schema declared.
No examples provided.
summary_day Daily summary ~43
Total hours logged for one calendar day (local date, default today), broken down per project.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Local date YYYY-MM-DD. Default: today. |
No output schema declared.
No examples provided.
summary_week Weekly summary ~29
Total hours logged in the week containing today (Mon-Sun, local dates), broken down per project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
target_check Check weekly hours goal ~29
Compare hours logged this week (Mon-Sun, local dates) against the weekly target from target_set.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
target_set Set weekly hours goal ~39
Set a weekly hours goal used by target_check. Stored locally.
| Name | Type | Req | Description |
|---|---|---|---|
| weekly_hours | number | yes | Target hours per week, e.g. 32 |
No output schema declared.
No examples provided.
timer_start Start timer ~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.
| 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, 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 |
No output schema declared.
No examples provided.
timer_status 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 Stop timer ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional note stored with the entry |
No output schema declared.
No examples provided.
How do I install the McpStamp Time Tracker MCP server?
McpStamp Time Tracker 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-time-tracker-timesheet-billable-h 'https://mcp.zovo.one/mcp/time-tracker'
What is the McpStamp Time Tracker MCP server?
McpStamp Time Tracker is an MCP server listed in the public MCP registry as io.github.theluckystrike/time-tracker-timesheet-billable-ho…. Track billable hours: timers, timesheets, weekly totals, CSV export, unbilled hours to invoices. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/time-tracker).
Is the McpStamp Time Tracker MCP server safe to use?
McpStamp Time Tracker scores 94 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 McpStamp Time Tracker MCP server expose?
McpStamp Time Tracker exposes 20 tools: license_status, license_activate, timer_start, timer_stop, timer_status, and 15 more. Their descriptions and schemas cost roughly 2,431 tokens of context every time the server is loaded.
Does the McpStamp Time Tracker MCP server require authentication?
Yes. McpStamp Time Tracker 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 McpStamp Time Tracker MCP server still maintained?
McpStamp Time Tracker is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.