Clockify MCP by usefulapi
REMOTE · CLOCKIFY.USEFULAPI.IO
Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time.
Available components
Last scanned (3 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 18 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3565 tokens (~169/item across 21 items; 21 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 Management27
- Stability observed for 8 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
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +3
- 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.1.0 → 1.2.0 functional
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 60
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 18 Oct 2026 · Probed https://clockify.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 clockify.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://clockify.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://clockify.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://clockify.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://clockify.usefulapi.io/mcp |
| Authorisation server | https://clockify.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://clockify.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/clockify/ |
| http (plaintext) | http://clockify.usefulapi.io/mcp | Inconclusive | 302 | http://clockify.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 →
clockify_create_client Create a client ~94
WRITE: add a client to a workspace. POST /v1/workspaces/{workspaceId}/clients.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Client address. |
| string | – | Client email. | |
| name | string | yes | Client name (unique in the workspace). |
| note | string | – | Note. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_create_project Create a project ~164
WRITE: create a project in a workspace (needs an admin or project-manager role, depending on workspace settings). POST /v1/workspaces/{workspaceId}/projects.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | Billable by default. |
| client_id | string | – | Client id (from clockify_list_clients). |
| color | string | – | Color, #RRGGBB. |
| is_public | boolean | – | Visible to the whole workspace. Default false: the project is private (visible to its members only). |
| name | string | yes | Project name, 2-250 characters (unique per client). |
| note | string | – | Project note. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_create_tag Create a tag ~68
WRITE: add a tag to a workspace. POST /v1/workspaces/{workspaceId}/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tag name (unique in the workspace). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_create_task Create a task ~113
WRITE: add a task to a project. POST /v1/workspaces/{workspaceId}/projects/{projectId}/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_ids | array | – | User ids to assign. |
| estimate | string | – | Time estimate, ISO 8601 duration such as PT1H30M. |
| name | string | yes | Task name. |
| project_id | string | yes | Project id. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_create_time_entry Log time or start a timer ~235
WRITE: add a time entry for yourself. With end = a finished entry (log time); without end = a running timer that starts at start (default now). A workspace with required custom fields may refuse it. POST /v1/workspaces/{workspaceId}/time-entries.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | Billable. Default: the project's billable setting (read from the project), else not billable. |
| description | string | – | What the time was spent on. |
| end | string | – | End time. Omit to start a running timer. |
| project_id | string | – | Project id (from clockify_list_projects). |
| start | string | – | Start time, ISO 8601 with a timezone. Default: now. |
| tag_ids | array | – | Tag ids (from clockify_list_tags). |
| task_id | string | – | Task id on that project (from clockify_list_tasks). |
| type | string | – | REGULAR (default) or BREAK. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_delete_time_entry Delete a time entry ~80
WRITE (destructive): permanently delete one time entry. It cannot be undone. DELETE /v1/workspaces/{workspaceId}/time-entries/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| time_entry_id | string | yes | Time entry id to delete. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_detailed_report Detailed report ~313
Every time entry in a date range across the workspace (user, project, client, task, tags, description, start/end, duration in seconds, amount), with totals; newest first, paged. POST reports /v1/workspaces/{workspaceId}/reports/detailed.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | true = only billable time, false = only non-billable. Default: both. |
| client_ids | array | – | Only these clients (ids). |
| description | string | – | Only entries whose description contains this text. |
| from | string | yes | First day of the report, yyyy-mm-dd (inclusive). On Clockify's FREE plan a report spans at most 31 days. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-200 (default 50). |
| project_ids | array | – | Only these projects (ids). |
| tag_ids | array | – | Only these tags (ids). |
| time_zone | string | – | IANA time zone the dates are read in, e.g. Europe/Berlin. Default: your Clockify profile's time zone. |
| to | string | yes | Last day of the report, yyyy-mm-dd (inclusive). |
| user_ids | array | – | Only these users (ids). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_get_current_user Get current user ~55
The Clockify user this API key belongs to: id, name, email, status, active and default workspace ids, and profile settings (time zone, week start, date/time format). GET /v1/user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
clockify_get_project Get a project ~106
One project by id: name, client, billable, color, note, estimate, duration tracked, rates and memberships. GET /v1/workspaces/{workspaceId}/projects/{projectId}.
| Name | Type | Req | Description |
|---|---|---|---|
| hydrated | boolean | – | true = include more detail (custom fields, estimates). |
| project_id | string | yes | Project id (from clockify_list_projects). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_get_running_timer Get running timer ~91
The timer that is running right now for a user (default: you), or running: false. GET /v1/workspaces/{workspaceId}/user/{userId}/time-entries?in-progress=true.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | – | User id. Default: you. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_get_time_entry Get a time entry ~111
One time entry by id: description, project, task, tags, billable, rates, custom fields and timeInterval. GET /v1/workspaces/{workspaceId}/time-entries/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| hydrated | boolean | – | true = embed the project, task and tag objects. |
| time_entry_id | string | yes | Time entry id (from clockify_list_time_entries). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_list_clients List clients ~145
List the clients of a workspace (id, name, email, address, currency, archived). GET /v1/workspaces/{workspaceId}/clients.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = only archived clients, false = only active ones. Default: both. |
| name | string | – | Only clients whose name contains this text. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-200 (default 50). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_list_projects List projects ~235
List the projects of a workspace: id, name, client, billable, public, color, archived, duration tracked, estimate and rates. Filter by name, client, user, billable or archived. GET /v1/workspaces/{workspaceId}/projects.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = only archived projects. Default: archived and active. |
| billable | boolean | – | true = only billable projects. Default: all. |
| client_ids | array | – | Only these clients (ids). |
| hydrated | boolean | – | true = include more detail (custom fields, memberships, estimates). |
| name | string | – | Only projects whose name contains this text. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-200 (default 50). |
| user_ids | array | – | Only these users (projects these users are members of) (ids). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_list_tags List tags ~139
List the tags of a workspace (id, name, archived). GET /v1/workspaces/{workspaceId}/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = only archived tags, false = only active ones. Default: both. |
| name | string | – | Only tags whose name contains this text. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-200 (default 50). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_list_tasks List project tasks ~170
List the tasks of a project (id, name, status, assignees, estimate, duration tracked). GET /v1/workspaces/{workspaceId}/projects/{projectId}/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | boolean | – | true = only active tasks, false = only done tasks. Default: both. |
| name | string | – | Only tasks whose name contains this text. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-200 (default 50). |
| project_id | string | yes | Project id (from clockify_list_projects). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_list_time_entries List time entries ~311
List the time entries of one user (default: you), newest first: id, description, project, task, tags, billable and timeInterval (start, end, ISO 8601 duration). Filter by time range, project, task, tags or description. For totals across users use clockify_summary_report. GET /v1/workspaces/{workspaceId}/user/{userId}/time-entries.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Only entries whose description contains this text. |
| end | string | – | Only entries starting before this time (ISO 8601 with a timezone). |
| hydrated | boolean | – | true = embed the project, task and tag objects instead of ids only. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-200 (default 50). |
| project_id | string | – | Only entries on this project. |
| start | string | – | Only entries starting at or after this time (ISO 8601 with a timezone). |
| tag_ids | array | – | Only these tags (ids). |
| task_id | string | – | Only entries on this task. |
| user_id | string | – | User id (from clockify_list_users). Default: you. Other users' entries need an admin or manager role. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_list_users List workspace users ~171
List the members of a workspace: id, name, email, status and settings. Filter by name, email, status or project access. GET /v1/workspaces/{workspaceId}/users.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Only users whose email contains this text. | |
| name | string | – | Only users whose name contains this text. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-200 (default 50). |
| project_id | string | – | Only users with access to this project. |
| status | string | – | Membership status filter. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_list_workspaces List workspaces ~76
List the Clockify workspaces you belong to: id, name, plan (featureSubscriptionType), subdomain, currencies and default hourly/cost rate. Use the id as workspace_id in other tools. GET /v1/workspaces.
| Name | Type | Req | Description |
|---|---|---|---|
| roles | array | – | Only workspaces where you have one of these roles. |
No output schema declared.
No examples provided.
clockify_stop_timer Stop running timer ~128
WRITE: stop the running timer of a user (default: you) at end (default now). Clockify answers 404 if no timer is running. PATCH /v1/workspaces/{workspaceId}/user/{userId}/time-entries.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Stop time, ISO 8601 with a timezone. Default: now. |
| user_id | string | – | User id. Default: you. Stopping someone else's timer needs an admin role. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_summary_report Summary report ~296
Totals of tracked time (seconds) and amounts for a date range across the workspace, grouped by up to 3 levels (default project → time entry), e.g. hours per user per project last month. Respects the filters. POST reports /v1/workspaces/{workspaceId}/reports/summary.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | true = only billable time, false = only non-billable. Default: both. |
| client_ids | array | – | Only these clients (ids). |
| description | string | – | Only entries whose description contains this text. |
| from | string | yes | First day of the report, yyyy-mm-dd (inclusive). On Clockify's FREE plan a report spans at most 31 days. |
| group_by | array | – | Grouping levels, outermost first (default [PROJECT, TIMEENTRY]). |
| project_ids | array | – | Only these projects (ids). |
| tag_ids | array | – | Only these tags (ids). |
| time_zone | string | – | IANA time zone the dates are read in, e.g. Europe/Berlin. Default: your Clockify profile's time zone. |
| to | string | yes | Last day of the report, yyyy-mm-dd (inclusive). |
| user_ids | array | – | Only these users (ids). |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
clockify_update_time_entry Update a time entry ~256
WRITE: change a time entry's start, end, description, project, task, tags or billable. Only the fields you pass change: the entry is read first and every other field (custom fields included) is sent back as it was. The entry is rewritten (PUT) from a fresh read, so an edit made to the same entry in between (e.g. in the Clockify app) can be lost. A new project without task_id clears the task. GET then PUT /v1/workspaces/{workspaceId}/time-entries/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | New billable flag. |
| description | string | – | New description. |
| end | string | – | New end time (also stops a running timer). |
| project_id | string | – | New project id. |
| start | string | – | New start time. |
| tag_ids | array | – | New tag ids (replaces the tags; [] removes them all). |
| task_id | string | – | New task id (on the entry's project). |
| time_entry_id | string | yes | Time entry id. |
| workspace_id | string | – | Workspace id (from clockify_list_workspaces). Default: your active workspace. |
No output schema declared.
No examples provided.
How do I install the Clockify MCP by usefulapi server?
Clockify MCP by usefulapi is a hosted endpoint at https://clockify.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 · clockify.usefulapi.io
claude mcp add --transport http io-usefulapi-clockify 'https://clockify.usefulapi.io/mcp'
What is the Clockify MCP by usefulapi server?
Clockify MCP by usefulapi is listed in the public MCP registry as io.usefulapi/clockify. Track time in Clockify: time entries, projects, clients, tags and reports; start, stop and log time. This page covers its hosted endpoint (https://clockify.usefulapi.io/mcp).
Is the Clockify MCP by usefulapi server safe to use?
Clockify MCP by usefulapi scores 66 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 Clockify MCP by usefulapi server expose?
Clockify MCP by usefulapi exposes 21 tools: clockify_get_current_user, clockify_list_workspaces, clockify_list_users, clockify_list_clients, clockify_list_projects, and 16 more. Their descriptions and schemas cost roughly 3,357 tokens of context every time the server is loaded.
Does the Clockify MCP by usefulapi server require authentication?
Yes. Clockify 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 Clockify MCP by usefulapi server still maintained?
Clockify MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.