WakaTime MCP by usefulapi
REMOTE · WAKATIME.USEFULAPI.IO
Read your WakaTime coding time: summaries, stats, projects, goals, commits and leaderboards.
Available components
Last scanned (4 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Productivity and Notes
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% 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 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
First indexed and scored.
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 17 Oct 2026 · Probed https://wakatime.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wakatime.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://wakatime.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://wakatime.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://wakatime.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://wakatime.usefulapi.io/mcp |
| Authorisation server | https://wakatime.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wakatime.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/wakatime/ |
| http (plaintext) | http://wakatime.usefulapi.io/mcp | Inconclusive | 302 | http://wakatime.usefulapi.io/mcp |
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 →
wakatime_get_all_time_since_today Get all-time total ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | Only this project's total. |
No output schema declared.
No examples provided.
wakatime_get_commit Get project commit ~110
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch (default: the repository's default branch). |
| hash | string | yes | Commit hash (from wakatime_list_commits). |
| project | string | yes | Project name exactly as WakaTime shows it (see wakatime_list_projects). |
No output schema declared.
No examples provided.
wakatime_get_durations Get durations for a day ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branches | string | – | Comma separated branch names; needs project. |
| date | string | yes | 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). |
No output schema declared.
No examples provided.
wakatime_get_goal Get goal ~62
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| goal_id | string | yes | Goal id (from wakatime_list_goals). |
No output schema declared.
No examples provided.
wakatime_get_heartbeats Get heartbeats for a day ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 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). |
No output schema declared.
No examples provided.
wakatime_get_insight Get insight ~199
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| insight_type | string | yes | – |
| 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). |
No output schema declared.
No examples provided.
wakatime_get_org_dashboard_summaries Get dashboard summaries for a day ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branches | string | – | Comma separated branch names; needs project. |
| dashboard_id | string | yes | Dashboard id. |
| date | string | yes | The day, yyyy-mm-dd. |
| org_id | string | yes | Organization id. |
| project | string | – | Only time logged to this project. |
No output schema declared.
No examples provided.
wakatime_get_org_member_summaries Get dashboard member summaries ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branches | string | – | Comma separated branch names; needs project. |
| dashboard_id | string | yes | Dashboard id. |
| end | string | – | Last day, yyyy-mm-dd, inclusive (with start). |
| member_id | string | yes | Member id (from wakatime_list_org_dashboard_members). |
| org_id | string | yes | 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). |
No output schema declared.
No examples provided.
wakatime_get_private_leaderboard Get private leaderboard ~164
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | 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. |
No output schema declared.
No examples provided.
wakatime_get_public_leaders Get public leaderboard ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
wakatime_get_stats Get coding stats ~163
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
wakatime_get_status_bar_today Get today's coding time ~62
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wakatime_get_summaries Get daily summaries ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
wakatime_get_user Get current user ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wakatime_list_commits List project commits ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Project name exactly as WakaTime shows it (see wakatime_list_projects). |
No output schema declared.
No examples provided.
wakatime_list_goals List goals ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
wakatime_list_machines List machines ~47
The machines (computers) that sent coding activity: id, name, host name, IP, timezone and last-seen time. GET /users/current/machine_names.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wakatime_list_org_dashboard_members List dashboard members ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard_id | string | yes | Dashboard id (from wakatime_list_org_dashboards). |
| org_id | string | yes | Organization id. |
| page | integer | – | Page number, from 1. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
wakatime_list_org_dashboards List organization dashboards ~87
The dashboards of an organization: id, name, timezone, member count and what the user may view or join. GET /users/current/orgs/{org}/dashboards.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | Organization id (from wakatime_list_orgs). |
| page | integer | – | Page number, from 1. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
wakatime_list_orgs List organizations ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
wakatime_list_private_leaderboards List private leaderboards ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
wakatime_list_projects List projects ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1. Pass the previous reply's next_page. |
| q | string | – | Filter project names by this search term. |
No output schema declared.
No examples provided.
wakatime_list_user_agents List editors and plugins used ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · wakatime.usefulapi.io
claude mcp add --transport http io-usefulapi-wakatime 'https://wakatime.usefulapi.io/mcp'
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.