# WakaTime MCP by usefulapi (remote · wakatime.usefulapi.io)

Read your WakaTime coding time: summaries, stats, projects, goals, commits and leaderboards.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `wakatime.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-wakatime/wakatime.md), [page](https://verifymcp.io/servers/io-usefulapi-wakatime/wakatime)

## Channel facts

- Endpoint: `https://wakatime.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2876 tokens (~125/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 99% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the WakaTime MCP by usefulapi server?

WakaTime MCP by usefulapi is a hosted endpoint at https://wakatime.usefulapi.io/mcp, 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-wakatime 'https://wakatime.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-wakatime": {
      "url": "https://wakatime.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-wakatime": {
      "type": "http",
      "url": "https://wakatime.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-wakatime]
url = "https://wakatime.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-wakatime": {
      "type": "remote",
      "url": "https://wakatime.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-wakatime --url 'https://wakatime.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-wakatime:
    url: "https://wakatime.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-wakatime": {
      "Transport": "http",
      "Url": "https://wakatime.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-wakatime -t streamable-http -u 'https://wakatime.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-wakatime": {
      "type": "http",
      "url": "https://wakatime.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 65, +1)

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

### 2026-10-15 (score 64, +1)

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

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (23)

### `wakatime_get_user` (~49 tokens)

Get current user

The WakaTime user this key belongs to: id, username, display name, email, timezone, plan, last plugin/project/branch and last heartbeat time. GET /users/current.

### `wakatime_get_summaries` (~225 tokens)

Get daily summaries

Coding activity as one summary per day for a date range: grand total plus breakdowns by project, language, editor, operating system, category, dependencies and machine, with cumulative total and daily average. Give start and end, or one named range. Use project (and branches) to also get per-branch and per-file entities. GET /users/current/summaries.

Input parameters:

- `branches` (string): Comma separated branch names; needs project.
- `end` (string): Last day, yyyy-mm-dd, inclusive (with start).
- `project` (string): Only time logged to this project.
- `range` (string): Alternative to start and end.
- `start` (string): First day, yyyy-mm-dd (with end).
- `timeout` (integer): Keystroke timeout in minutes (default: the user's preference).
- `timezone` (string): IANA timezone such as Europe/Berlin (default: the user's timezone).
- `writes_only` (boolean): Only count heartbeats that were file writes (default: the user's preference).

### `wakatime_get_stats` (~163 tokens)

Get coding stats

Aggregated coding stats for a range: total time, daily average, best day, AI vs human line changes, and the full breakdown by language, project, editor, operating system, category, dependencies and machine. If the reply says it is still calculating, call again shortly. GET /users/current/stats/{range}.

Input parameters:

- `range` (string): Time range: last_7_days, last_30_days, last_6_months, last_year, all_time, a year (2026) or a month (2026-09).
- `timeout` (integer): Keystroke timeout in minutes (default: the user's preference).
- `writes_only` (boolean): Only count heartbeats that were file writes (default: the user's preference).

### `wakatime_get_all_time_since_today` (~60 tokens)

Get all-time total

Total coding time since the user's WakaTime account (or one project) was created, with daily average and the range covered. GET /users/current/all_time_since_today.

Input parameters:

- `project` (string): Only this project's total.

### `wakatime_get_status_bar_today` (~62 tokens)

Get today's coding time

Today's coding activity as shown in an editor status bar: grand total plus breakdowns by project, language, editor and more. Cached data only; an empty summary means the cache is still being filled. GET /users/current/status_bar/today.

### `wakatime_get_insight` (~199 tokens)

Get insight

One WakaTime insight for a range: stats, weekdays (average per weekday), days (per-day totals, optionally one weekday), ai_days, best_day, daily_average, or a breakdown by projects, languages, editors, categories, machines or operating_systems. GET /users/current/insights/{insight_type}/{range}.

Input parameters:

- `insight_type` (string, required)
- `range` (string): Time range: last_7_days, last_30_days, last_6_months, last_year, all_time, a year (2026) or a month (2026-09).
- `timeout` (integer): Keystroke timeout in minutes (default: the user's preference).
- `weekday`: Only for insight_type 'days': a weekday, 0-6 or monday..sunday.
- `writes_only` (boolean): Only count heartbeats that were file writes (default: the user's preference).

### `wakatime_get_durations` (~185 tokens)

Get durations for a day

The coding sessions (durations) of one day, each with start time, length in seconds and the project (or other slice) it belongs to. Needs the read_heartbeats scope for OAuth tokens. GET /users/current/durations.

Input parameters:

- `branches` (string): Comma separated branch names; needs project.
- `date` (string, required): The day, yyyy-mm-dd, in the user's timezone.
- `project` (string): Only durations for this project.
- `slice_by` (string): What to slice durations by (default project).
- `timeout` (integer): Keystroke timeout in minutes (default: the user's preference).
- `timezone` (string): IANA timezone such as Europe/Berlin (default: the user's timezone).
- `writes_only` (boolean): Only count heartbeats that were file writes (default: the user's preference).

### `wakatime_get_heartbeats` (~169 tokens)

Get heartbeats for a day

The raw heartbeats (activity pings from editor plugins) of one day: entity (file path or domain), type, category, project, branch, language, time, lines and AI line changes. Large days are cut to `limit` heartbeats starting at `offset`; total_heartbeats says how many the day has. Needs the read_heartbeats scope for OAuth tokens. GET /users/current/heartbeats.

Input parameters:

- `date` (string, required): The day, yyyy-mm-dd, 12am to 11:59pm in the user's timezone.
- `limit` (integer): Return at most this many heartbeats (default 200).
- `offset` (integer): Skip this many heartbeats first (to read a busy day in slices; default 0).

### `wakatime_list_projects` (~88 tokens)

List projects

The user's WakaTime projects with id, name, repository, color, clients, first and last heartbeat time and badge/public-url flags. Optionally filter by a name search. GET /users/current/projects.

Input parameters:

- `page` (integer): Page number, from 1. Pass the previous reply's next_page.
- `q` (string): Filter project names by this search term.

### `wakatime_list_machines` (~47 tokens)

List machines

The machines (computers) that sent coding activity: id, name, host name, IP, timezone and last-seen time. GET /users/current/machine_names.

### `wakatime_list_user_agents` (~47 tokens)

List editors and plugins used

The editor and plugin user agents that sent coding activity: editor, version, OS, AI model if any, and last-seen time. GET /users/current/user_agents.

### `wakatime_list_commits` (~141 tokens)

List project commits

Commits of a WakaTime project with the time spent coding on each (needs a connected repository). Filter by author or branch; paged. Needs the read_heartbeats scope for OAuth tokens. GET /users/current/projects/{project}/commits.

Input parameters:

- `author` (string): Only commits by this author (WakaTime username).
- `branch` (string): Branch (default: the repository's default branch).
- `page` (integer): Page number, from 1. Pass the previous reply's next_page.
- `project` (string, required): Project name exactly as WakaTime shows it (see wakatime_list_projects).

### `wakatime_get_commit` (~110 tokens)

Get project commit

One commit of a WakaTime project by hash, with the time spent coding on it. Needs the read_heartbeats scope for OAuth tokens. GET /users/current/projects/{project}/commits/{hash}.

Input parameters:

- `branch` (string): Branch (default: the repository's default branch).
- `hash` (string, required): Commit hash (from wakatime_list_commits).
- `project` (string, required): Project name exactly as WakaTime shows it (see wakatime_list_projects).

### `wakatime_list_goals` (~82 tokens)

List goals

The user's coding goals: title, type, target seconds, status, chart data per period, languages/projects/editors it covers and who it is shared with. Needs the read_goals scope for OAuth tokens. GET /users/current/goals.

Input parameters:

- `page` (integer): Page number, from 1. Pass the previous reply's next_page.

### `wakatime_get_goal` (~62 tokens)

Get goal

One goal by id with its chart data (cached; an empty chart means the cache is still building, retry shortly). GET /users/current/goals/{goal}.

Input parameters:

- `goal_id` (string, required): Goal id (from wakatime_list_goals).

### `wakatime_list_orgs` (~81 tokens)

List organizations

The WakaTime organizations the user belongs to: id, name, people count, keystroke timeout and timezone preferences and what the user may do. Needs the read_orgs scope for OAuth tokens. GET /users/current/orgs.

Input parameters:

- `page` (integer): Page number, from 1. Pass the previous reply's next_page.

### `wakatime_list_org_dashboards` (~87 tokens)

List organization dashboards

The dashboards of an organization: id, name, timezone, member count and what the user may view or join. GET /users/current/orgs/{org}/dashboards.

Input parameters:

- `org_id` (string, required): Organization id (from wakatime_list_orgs).
- `page` (integer): Page number, from 1. Pass the previous reply's next_page.

### `wakatime_list_org_dashboard_members` (~105 tokens)

List dashboard members

The members of an organization dashboard: id, username, full name, email, photo and whether their activity is view-only hidden. GET /users/current/orgs/{org}/dashboards/{dashboard}/members.

Input parameters:

- `dashboard_id` (string, required): Dashboard id (from wakatime_list_org_dashboards).
- `org_id` (string, required): Organization id.
- `page` (integer): Page number, from 1. Pass the previous reply's next_page.

### `wakatime_get_org_dashboard_summaries` (~114 tokens)

Get dashboard summaries for a day

One day of coding activity for every developer on an organization dashboard (grand total plus breakdowns per member). GET /users/current/orgs/{org}/dashboards/{dashboard}/summaries.

Input parameters:

- `branches` (string): Comma separated branch names; needs project.
- `dashboard_id` (string, required): Dashboard id.
- `date` (string, required): The day, yyyy-mm-dd.
- `org_id` (string, required): Organization id.
- `project` (string): Only time logged to this project.

### `wakatime_get_org_member_summaries` (~173 tokens)

Get dashboard member summaries

One dashboard member's coding activity as daily summaries for a date range (give start and end, or a named range). GET /users/current/orgs/{org}/dashboards/{dashboard}/members/{member}/summaries.

Input parameters:

- `branches` (string): Comma separated branch names; needs project.
- `dashboard_id` (string, required): Dashboard id.
- `end` (string): Last day, yyyy-mm-dd, inclusive (with start).
- `member_id` (string, required): Member id (from wakatime_list_org_dashboard_members).
- `org_id` (string, required): Organization id.
- `project` (string): Only time logged to this project.
- `range` (string): Alternative to start and end.
- `start` (string): First day, yyyy-mm-dd (with end).

### `wakatime_list_private_leaderboards` (~77 tokens)

List private leaderboards

The private leaderboards the user is in: id, name, time range, member count and edit rights. Needs the read_private_leaderboards scope for OAuth tokens. GET /users/current/leaderboards.

Input parameters:

- `page` (integer): Page number, from 1. Pass the previous reply's next_page.

### `wakatime_get_private_leaderboard` (~164 tokens)

Get private leaderboard

The ranking of a private leaderboard: rank, member and total coding time (or AI lines / AI spend) per language, country and board type; paged (without page it starts at the user's own page). GET /users/current/leaderboards/{board}.

Input parameters:

- `board_id` (string, required): Leaderboard id (from wakatime_list_private_leaderboards).
- `board_type` (string): Ranking: time (hours coded, default), manual (excluding AI coding), ai (AI lines) or spend (AI spend).
- `country_code` (string): Two-letter country code.
- `language` (string): Only this language.
- `page` (integer): Page number, from 1. Pass the previous reply's next_page.

### `wakatime_get_public_leaders` (~171 tokens)

Get public leaderboard

WakaTime's public leaderboard of the most active coders over the last 7 days, filterable by language, country, hireable badge and ranking type; paged. Each leader is reduced to rank, name, username, country, total and daily-average time and top 3 languages. GET /leaders.

Input parameters:

- `board_type` (string): Ranking: time (hours coded, default), manual (excluding AI coding), ai (AI lines) or spend (AI spend).
- `country_code` (string): Two-letter country code.
- `is_hireable` (boolean): Only coders with the hireable badge.
- `language` (string): Only this language.
- `page` (integer): Page number, from 1. Pass the previous reply's next_page.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-wakatime/wakatime#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 61

## Common questions

### What is the WakaTime MCP by usefulapi server?

WakaTime MCP by usefulapi is listed in the public MCP registry as io.usefulapi/wakatime. Read your WakaTime coding time: summaries, stats, projects, goals, commits and leaderboards. This page covers its hosted endpoint (https://wakatime.usefulapi.io/mcp).

### Is the WakaTime MCP by usefulapi server safe to use?

WakaTime MCP by usefulapi scores 65 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 WakaTime MCP by usefulapi server expose?

WakaTime MCP by usefulapi exposes 23 tools: wakatime_get_user, wakatime_get_summaries, wakatime_get_stats, wakatime_get_all_time_since_today, wakatime_get_status_bar_today, and 18 more. Their descriptions and schemas cost roughly 2,661 tokens of context every time the server is loaded.

### Does the WakaTime MCP by usefulapi server require authentication?

Yes. WakaTime MCP by usefulapi 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 WakaTime MCP by usefulapi server still maintained?

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

## Links

- Remote endpoint: https://wakatime.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/wakatime/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-wakatime/wakatime.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-wakatime/wakatime.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-wakatime/wakatime