MCP.Market

Timesheets MCP server

online · 100% uptime
by theluckystrike·io.github.theluckystrike/timesheets·v0.21.1·1 stars
No reviews yet

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

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed Timesheets yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Timesheets tools (14, 1 write)

write = sends, deletes, buys or posts
  • entry_addFree

    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.

  • entry_deletewrite actionFree

    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.

  • entry_editFree

    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.

  • entry_listFree

    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.

  • entry_mark_billedFree

    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.

  • export_csvFree

    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.

  • invoice_summaryFree

    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.

  • license_activateFree

    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.

  • license_statusFree

    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.

  • project_set_rateFree

    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.

  • reportFree

    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.

  • timer_startFree

    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.

  • timer_statusFree

    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.

  • timer_stopFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • Live reliabilityremote reachable in 1376ms20/20
  • Tool poisoning14 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Timesheets compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
14
the typical server has 7
Tools that change things
7%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
8 ms
faster than 99% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

What its tools let an agent do: 13 read · 1 change

Release history: 2 versions in the registry since 2026-09-12, latest 2026-09-23, typically one every 11 days.

Install Timesheets in Claude Code, Cursor or VS Code

claude mcp add --transport http timesheets https://mcp.zovo.one/mcp/timesheets
Add to Cursor

What the publisher says

From the Timesheets repository's README, as published. We do not edit it. Read it on GitHub

MCP servers by theluckystrike

<!-- gen:badge --> <!-- /gen:badge -->

Practical Model Context Protocol servers for people who work inside Claude, Cursor and other MCP clients. Every server runs locally over stdio, keeps all data on your machine, and has a genuinely useful free tier. Pro unlocks the limits for a one-time payment: $19 per server or $39 for the bundle, lifetime.

<!-- gen:counts --> 46 servers plus the office-suite aggregator, 45 of them also reachable as a hosted endpoint with no install. <!-- /gen:counts -->

No install? Use any server instantly as a hosted endpoint: https://mcp.zovo.one/mcp/ — or browse the catalog at mcp.zovo.one.

<!-- gen:install -->

That is the invoice server answering a real prompt: a client, some hours, a VAT rate, and a numbered PDF at the end. Every server in the table below has a demo like it.

Two ways to run any of these, both working today.

  1. One click. Download the server's .mcpb bundle from the latest release and open it in Claude Desktop. No terminal, no config file.
  2. No install at all. Point a client at https://mcp.zovo.one/mcp/. GET https://mcp.zovo.one/mcp/connect mints a free token and prints a ready URL for each server.

A third way is coming and does not work yet: the npm packages are unpublished, so npx -y @theluckystrike/mcp- returns 404 today. The commands below are written for the day it is published; use one of the two paths above until then. <!-- /gen:install -->

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-03restoreB → Ascore 88

Timesheets: common questions

Is Timesheets MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Timesheets safety report
How do I install Timesheets?
It runs remotely at mcp.zovo.one. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Timesheets need an API key?
Yes. The registry entry asks for MCP_LICENSE_KEY, Authorization.
Is Timesheets maintained?
The last commit was 36 days ago (2026-09-29). The latest release is v0.21.1.
Is Timesheets up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Timesheets compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 14 (the typical server has 7); tools that change things 7% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.