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.

McpStamp Timer Tracking

MCPB · TIME-TRACKER.MCPB · 2 COMPONENTS

Run a work timer, log hours per project and rate, and turn unbilled time into invoice lines.

−14 this week 47 Trust /100

Last scanned (13 hours ago)

Scores higher than 77% of MCPB servers

Category Finance and Payments

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
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 30 of 92 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.

What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityNo malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 18 Nov 26 −14
    • Stability: pass → unverified ▼ security
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 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.

  • 9 Nov 26 +1

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

  • 7 Nov 26 +1

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

  • 6 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 4 Nov 26 +1
    • Maintenance: unverified → pass ▲ functional
  • 2 Nov 26 +55
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • MCP protocol: unverified → pass ▲ functional
    • Dependency health: unverified → 0.85 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • License: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Licence: MIT functional
    • Package version: 0.22.5 → 0.21.0 functional
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 21 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/time-tracker.mcpb@0.21.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
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
billableboolean–Default true; set false for non-billable work
currencystring–Currency of the rate: EUR, USD, GBP, PLN, or words like 'euros'. Defaults to the project currency, else USD.
endstring–ISO 8601 end time (or use minutes)
minutesnumber–Duration in minutes (alternative to end)
notestring–Optional note
projectstringyesProject 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')
startstringyesISO 8601 start time, e.g. 2026-09-02T09:00:00
tagsarray–Optional tags
taskstring–What 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––
currencystring–Currency of the rate, e.g. EUR
endstring–ISO 8601
idstringyesEntry id from entry_list
minutesnumber–New duration in minutes, keeps start
notestring––
projectstring––
rate––Hourly rate override for this entry, a number or words like '90 euros'
startstring–ISO 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
fromstring–ISO date/time lower bound
limitinteger–Maximum rows, newest first (default 50)
projectstring–Filter by project name
tostring–ISO 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_atstring–ISO timestamp of the stamp, defaults to now
fromstring–ISO date/time start of the billed period, used with project
idsarray–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_numberstringyesThe invoice these hours were put on, e.g. INV-2026-0001
projectstring–Project or client, used with from and to instead of ids; every billable entry in that range is stamped.
tostring–ISO 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
fromstring–ISO date/time lower bound. On the free tier the export is clamped to the last 7 days; Pro exports the full history.
pathstring–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.
projectstring–Optional project filter
tostring–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 ~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_onlyboolean–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 ~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_existingboolean–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…
currencystring–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–yesHourly 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_missingboolean–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…
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
formatstring–table (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_bystring–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.
projectstring–Optional 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_onlyboolean–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.

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
currencystring–Currency 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.
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.
tagsarray–Free-form tags, e.g. ['dev','meeting']
taskstring–What 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
notestring–Optional note stored with the entry

No output schema declared.

No examples provided.

Install

How do I install the McpStamp Timer Tracking MCP server?

McpStamp Timer Tracking ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, c59343d432c1550a8140c386cda28e96d05cfc706c67b44bdaa897e77db2daf0; the commands to do that are on this page. If it does not match, do not open it.

mcpb · time-tracker.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

c59343d432c1550a8140c386cda28e96d05cfc706c67b44bdaa897e77db2daf0

macOS / Linux

echo "c59343d432c1550a8140c386cda28e96d05cfc706c67b44bdaa897e77db2daf0  time-tracker.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\time-tracker.mcpb).Hash -eq "c59343d432c1550a8140c386cda28e96d05cfc706c67b44bdaa897e77db2daf0"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the McpStamp Timer Tracking MCP server?

McpStamp Timer Tracking is an MCP server listed in the public MCP registry as io.github.theluckystrike/timer-tracking. Run a work timer, log hours per project and rate, and turn unbilled time into invoice lines. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/time-tracker.mcpb).

Is the McpStamp Timer Tracking MCP server safe to use?

McpStamp Timer Tracking 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 McpStamp Timer Tracking MCP server expose?

McpStamp Timer Tracking 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 McpStamp Timer Tracking MCP server under?

McpStamp Timer 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.

What did VerifyMCP test on the McpStamp Timer Tracking MCP server?

VerifyMCP ran 14 checks on McpStamp Timer Tracking, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about McpStamp Timer Tracking: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.