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.

Wakatime

NPM · @PIPEWORX/MCP-WAKATIME · 2 COMPONENTS

WakaTime MCP.

+18 this week 79 Trust /100

Last scanned (11 hours ago)

Scores higher than 62% of npm servers

Category Data and Analytics

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-wakatime). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 1311 tokens (~109/item across 12 items; 12 tools + 0 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% 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
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
What we tested

Checks we ran (16)

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

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.

  • 5 Nov 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 61

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-wakatime@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-wakatime
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-wakatime/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3575130509
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:97efb8a06f6461a85d3f74c0ea0d7d93495b850b1c51e22ed7d75a2236c62b839c1209728343a15cf281db9c6e8ffd1fd0710421ca1341b1fd2658cf6

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~1,257 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
commits ~191

List the commits WakaTime has recorded for one project belonging to a WakaTime user, given user_id (or "current") and the project name, with optional author, branch, and page. Returns each commit hash, message, author, branch, timestamps, and the coding time WakaTime attributes to it. Answers what has been committed to a project tracked by WakaTime and how much editor time went into it. Requires your own WakaTime personal OAuth token as _apiKey.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
authorstring––
branchstring––
pagenumber––
projectstringyes–
user_idstringyes–

No output schema declared.

No examples provided.

current_user ~82

Profile of the WakaTime account that owns your OAuth token. Requires your own WakaTime personal OAuth token as _apiKey.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.

No output schema declared.

No examples provided.

durations ~167

Fetch WakaTime coding durations (start/end timestamps with project and file) for a single day (date required, YYYY-MM-DD); optionally slice_by entity/language/branch for granular session data. Requires your own WakaTime personal OAuth token as _apiKey.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
branchesstring––
datestringyes–
projectstring––
slice_bystring––
timeoutnumber––
timezonestring––
user_idstringyes–
writes_onlyboolean––

No output schema declared.

No examples provided.

editors ~32

Fetch WakaTime's public editor usage statistics showing relative popularity of code editors and IDEs across all WakaTime users.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

goals ~87

User's goals. Requires your own WakaTime personal OAuth token as _apiKey.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
pagenumber––
user_idstringyes–

No output schema declared.

No examples provided.

heartbeats ~91

Raw heartbeats for a date. Requires your own WakaTime personal OAuth token as _apiKey.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
datestringyes–
user_idstringyes–

No output schema declared.

No examples provided.

leaders ~59

Fetch WakaTime's public coding leaderboard; optionally filter by language or country_code and paginate; returns ranked users with display names and weekly coding totals.

NameTypeReqDescription
country_codestring––
languagestring––
pagenumber––

No output schema declared.

No examples provided.

meta ~35

Fetch WakaTime API metadata including current server time and available timezones; useful for validating timezone strings before passing them to summaries or durations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

projects ~87

User's projects. Requires your own WakaTime personal OAuth token as _apiKey.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
qstring––
user_idstringyes–

No output schema declared.

No examples provided.

stats ~163

Fetch aggregated WakaTime coding stats for a user over a range ("last_7_days", "last_30_days", "last_6_months", "last_year", "all_time"); returns totals and rankings by language, project, editor, and OS. Keyless for public profiles; pass your OAuth token as _apiKey for private ones.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
projectstring––
rangestringyes–
timeoutnumber––
user_idstringyes–
writes_onlyboolean––

No output schema declared.

No examples provided.

summaries ~168

Fetch WakaTime daily coding summaries for a user over a date range (start/end required, YYYY-MM-DD); returns per-day breakdowns by project, language, editor, OS, and category in seconds. Requires your own WakaTime personal OAuth token as _apiKey.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
branchesstring––
endstringyes–
projectstring––
startstringyes–
timeoutnumber––
timezonestring––
user_idstringyes–
writes_onlyboolean––

No output schema declared.

No examples provided.

user ~95

Public WakaTime profile for a user_id/username; keyless for public profiles, pass your OAuth token as _apiKey for your own or private ones.

NameTypeReqDescription
_apiKeystring–Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
user_idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Wakatime MCP server?

Wakatime runs locally as an npm package, launched with npx -y @pipeworx/mcp-wakatime. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-wakatime

# add to Claude Code
claude mcp add pipeworx-io-wakatime -- npx -y @pipeworx/mcp-wakatime
Common questions

What is the Wakatime MCP server?

Wakatime is an MCP server listed in the public MCP registry as io.github.pipeworx-io/wakatime. WakaTime MCP. This page covers its npm package (@pipeworx/mcp-wakatime).

Is the Wakatime MCP server safe to use?

Wakatime scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Wakatime MCP server expose?

Wakatime exposes 12 tools: current_user, user, summaries, stats, durations, and 7 more. Their descriptions and schemas cost roughly 1,257 tokens of context every time the server is loaded.

Is the Wakatime MCP server still maintained?

Wakatime is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Wakatime MCP server under?

Wakatime 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 Wakatime MCP server?

VerifyMCP ran 16 checks on Wakatime, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.