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

Timebook

NPM · @SQUIDCODE/TIMEBOOK · 2 COMPONENTS · SCANNED AUG 3

Track time on usetimebook.com - start/stop timers, log entries, list projects/clients.

+31 this week 77 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (108 of 112), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (108 of 112), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to squidcode/timebook-cli). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 58 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 898 tokens (~74/item across 12 items; 12 tools + 0 resources), lean.Pass
  • 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.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.

npm · @squidcode/timebook

# add to Claude Code
claude mcp add squidcode-timebook -- npx -y @squidcode/timebook
# add to Codex CLI
codex mcp add squidcode-timebook -- npx -y @squidcode/timebook
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "squidcode-timebook": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@squidcode/timebook"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add squidcode-timebook --command npx --arg -y --arg @squidcode/timebook
# ~/.hermes/config.yaml
mcp_servers:
  squidcode-timebook:
    command: "npx"
    args: ["-y", "@squidcode/timebook"]
// mcp.json
{
  "mcpServers": {
    "squidcode-timebook": {
      "command": "npx",
      "args": [
        "-y",
        "@squidcode/timebook"
      ]
    }
  }
}
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.

  • 2 Aug 26 +56
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: squidcode/timebook-cli security
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • MCP protocol: unverified → pass functional
    • Maintenance: unverified → pass functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 46

    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 3 Aug 2026 · Analysed npm/@squidcode/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
squidcode/timebook-cli
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/squidcode/timebook-cli/.github/workflows/release.yml@refs/heads/main
Rekor log index:
1735690527
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:e0aa8a189c472fa7fecad98231051d5415e6da50b0e456b739ac23bbdf77acf3871c0f8963512890505946cec14742fe9787d5e6e1e53da788e6c8ff1
Discovery method:
attestation_endpoint
Dependencies 108 packages

108 packages in the resolved dependency tree · 108 deprecated · 32 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 12 exposed · ~898 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.

Tool Tokens
create_client ~64

Create a client (the person/company you bill). Needed before any project or time entry can exist. Typical first step on a fresh account.

NameTypeReqDescription
emailstringOptional billing/contact email.
namestringyesClient name, e.g. 'Acme Corp'.

No output schema declared.

No examples provided.

create_project ~75

Create a project under a client. Time entries are always tracked against a project. Typical second step on a fresh account, after create_client.

NameTypeReqDescription
clientstringyesClient - id or exact name.
descriptionstringOptional project description.
namestringyesProject name, e.g. 'Website redesign'.

No output schema declared.

No examples provided.

delete_entry ~48

Delete a time entry. Server enforces: not invoiced, and either this token created it or the caller is an admin / web session.

NameTypeReqDescription
idstringyesEntry id (uuid).

No output schema declared.

No examples provided.

get_active_timer ~30

Return the currently running timer (project, description, started_at), or null if no timer is running.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_clients ~17

List all clients available to the current token.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_entries ~126

List recent time entries, optionally filtered by project and/or date range. Returns at most 50 entries by default; pass a higher `limit` to see more.

NameTypeReqDescription
endDatestringISO-8601 — only entries whose start time is on or before this.
limitintegerMaximum number of entries to return. Defaults to 50.
projectstringOptional project id or exact name. Omit to list across all projects.
startDatestringISO-8601 — only entries whose start time is on or after this.

No output schema declared.

No examples provided.

list_projects ~28

List all projects available to the current token. Returns id, name, and client for each project.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

log_time ~202

Log a manual (past) time entry. Provide either `duration` (relative to now), or both `startTime` and `endTime` (absolute ISO-8601 timestamps).

NameTypeReqDescription
descriptionstringWhat the user worked on.
durationstringHow long the work took. Accepts "1h", "45m", "1h30m", "1.5h", "1:30", or "90" (interpreted as minutes).
endTimestringISO-8601 end time. Required if duration is omitted.
projectstringyesProject id (UUID) or exact project name.
ratestringOptional rate id or exact rate name (e.g. "Software Development").
startTimestringISO-8601 start time (e.g. "2026-05-04T09:00:00Z"). Required if duration is omitted.

No output schema declared.

No examples provided.

start_timer ~98

Start a timer on a project. Stops any other running timer first — Timebook allows only one active timer at a time.

NameTypeReqDescription
descriptionstringWhat the user is working on (visible in the time entry).
projectstringyesProject id (UUID) or exact project name. Use list_projects to discover.
ratestringOptional rate id (UUID) or exact rate name (e.g. "Software Development").

No output schema declared.

No examples provided.

stop_timer ~26

Stop the currently running timer. Returns { stopped: false } if no timer was running.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_entry ~162

Edit one or more fields on an existing time entry. Any combination is valid; unset fields are left as-is. Server-enforced authorship rule: this token can only edit entries it created itself (sessions and admins bypass).

NameTypeReqDescription
descriptionstring|nullNew description / note. Pass empty string or null to clear.
durationstringNew duration, e.g. "1h30m" or "45m".
endTimestringISO-8601 end time.
idstringyesEntry id (uuid).
projectstringReassign — project id or name.
ratestringNew rate — id or name.
startTimestringISO-8601 start time.

No output schema declared.

No examples provided.

whoami ~22

Return the currently authenticated Timebook user (id, email, name).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.