TimeTac MCP by usefulapi
REMOTE · TIMETAC.USEFULAPI.IO
Read hours, absences and projects; start timers, add entries, approve leave in TimeTac.
Available components
Last scanned (10 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
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 5 Nov 2026 · Probed https://timetac.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 timetac.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://timetac.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/timetac/ |
| http (plaintext) | http://timetac.usefulapi.io/mcp | Inconclusive | 302 | http://timetac.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 →
timetac_approve_absence Approve absence ~72
WRITE: approve an open absence request. The employee is notified by TimeTac. TimeTac API: PUT absences/approve.
| Name | Type | Req | Description |
|---|---|---|---|
| absence_id | integer | yes | The absence request id (from timetac_list_absences). |
| comment | string | – | Optional comment shown to the employee. |
No output schema declared.
No examples provided.
timetac_create_absence Request absence ~203
WRITE: create an absence or leave request for a user. Each call creates a new request, so do not repeat it. type_id is the category (1 holiday, 2 overtime reduction, 3 other paid leave); subtype_id picks the leave type from timetac_list_absence_types. TimeTac API: POST absences/create.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | number | – | Requested duration, in the unit of duration_unit. |
| duration_unit | string | – | d = days, hs = hours. |
| from_date | string | yes | – |
| request_comment | string | – | – |
| subtype_id | integer | – | Specific leave type inside the category (for example which other paid leave). See timetac_list_absence_types. |
| to_date | string | yes | – |
| type_id | integer | yes | Absence category: 1 = holiday, 2 = overtime reduction, 3 = other paid leave. |
| user_id | integer | yes | – |
No output schema declared.
No examples provided.
timetac_create_time_tracking Add time entry ~130
WRITE: add a finished time entry for a user. Each call creates a new entry, so do not repeat it. TimeTac API: POST timeTrackings/create.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | yes | – |
| end_time_timezone | string | yes | IANA time zone, for example Europe/Vienna. |
| notes | string | – | – |
| start_time | string | yes | – |
| start_time_timezone | string | yes | IANA time zone, for example Europe/Vienna. |
| task_id | integer | yes | The task to book the time on. |
| user_id | integer | yes | – |
No output schema declared.
No examples provided.
timetac_current_time_trackings Running timers ~57
List the timers that run right now (who is clocked in, on which task). TimeTac API: GET timeTrackings/current.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | – | Only the running timer of this user id. |
No output schema declared.
No examples provided.
timetac_get_user Get user ~58
Get one employee by user id. Only work-related fields are returned (no credentials, payroll, address or birth data). TimeTac API: GET users/read?id=.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | The TimeTac user id. |
No output schema declared.
No examples provided.
timetac_list_absence_types List absence types ~71
List the absence types of the account (holiday, sick leave, special leave) with their ids. TimeTac API: GET absenceTypes/read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows to return (API default 100). |
| offset | integer | – | Skip this many rows (paging). |
No output schema declared.
No examples provided.
timetac_list_absences List absences ~253
List absence and leave requests (holiday, sick leave and others) with dates, duration and approval status. from_date/to_date keep requests that overlap the range, on the returned page only. TimeTac API: GET absences/read.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Keep requests that end on or after this date. |
| limit | integer | – | Maximum rows to return (API default 100). |
| offset | integer | – | Skip this many rows (paging). |
| since | string | – | Only rows modified since this date-time, for example 2026-10-01 00:00:00. Dates older than 3 months return everything. |
| status | integer | – | Only this status code (0 = open; see the TimeTac docs for the others). |
| subtype_id | integer | – | Only this leave type inside the category (see timetac_list_absence_types). |
| to_date | string | – | Keep requests that start on or before this date. |
| type_id | integer | – | Only this absence category: 1 = holiday, 2 = overtime reduction, 3 = other paid leave. |
| user_id | integer | – | Only requests of this user id. |
No output schema declared.
No examples provided.
timetac_list_departments List departments ~57
List departments with ids and parent departments. TimeTac API: GET departments/read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows to return (API default 100). |
| offset | integer | – | Skip this many rows (paging). |
No output schema declared.
No examples provided.
timetac_list_projects List projects ~123
List projects (task tree nodes that group tasks) with ids, deadlines and status. TimeTac API: GET projects/read.
| Name | Type | Req | Description |
|---|---|---|---|
| is_done | boolean | – | Only finished (true) or open (false) projects. |
| limit | integer | – | Maximum rows to return (API default 100). |
| offset | integer | – | Skip this many rows (paging). |
| since | string | – | Only rows modified since this date-time, for example 2026-10-01 00:00:00. Dates older than 3 months return everything. |
No output schema declared.
No examples provided.
timetac_list_tasks List tasks ~139
List tasks that time can be booked on, with their project (mother_id) and status. TimeTac API: GET tasks/read.
| Name | Type | Req | Description |
|---|---|---|---|
| is_done | boolean | – | Only finished (true) or open (false) tasks. |
| limit | integer | – | Maximum rows to return (API default 100). |
| mother_id | integer | – | Only tasks of this project id. |
| offset | integer | – | Skip this many rows (paging). |
| since | string | – | Only rows modified since this date-time, for example 2026-10-01 00:00:00. Dates older than 3 months return everything. |
No output schema declared.
No examples provided.
timetac_list_teams List teams ~56
List teams with ids and names. TimeTac API: GET teams/read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows to return (API default 100). |
| offset | integer | – | Skip this many rows (paging). |
No output schema declared.
No examples provided.
timetac_list_time_trackings List time trackings ~216
List time entries (start, end, duration, task, notes, approval), newest first. Filter by user, task or approval. start_date/end_date filter the returned page only; page with offset. TimeTac API: GET timeTrackings/read.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_by_admin | boolean | – | Only approved (true) or not approved (false) entries. |
| end_date | string | – | Keep entries that start on or before this date. |
| limit | integer | – | Maximum rows to return (API default 100). |
| offset | integer | – | Skip this many rows (paging). |
| since | string | – | Only rows modified since this date-time, for example 2026-10-01 00:00:00. Dates older than 3 months return everything. |
| start_date | string | – | Keep entries that start on or after this date. |
| task_id | integer | – | Only entries booked on this task id. |
| user_id | integer | – | Only entries of this user id. |
No output schema declared.
No examples provided.
timetac_list_users List users ~161
List employees (users) of the TimeTac account: id, name, department, active flag, entry/exit dates. Only work-related fields are returned (no credentials, payroll, address or birth data). TimeTac API: GET users/read.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Only active (true) or inactive (false) users. |
| department_id | integer | – | Only users of this department id. |
| limit | integer | – | Maximum rows to return (API default 100). |
| offset | integer | – | Skip this many rows (paging). |
| since | string | – | Only rows modified since this date-time, for example 2026-10-01 00:00:00. Dates older than 3 months return everything. |
No output schema declared.
No examples provided.
timetac_reject_absence Reject absence ~72
WRITE: reject an open absence request. The employee is notified by TimeTac. TimeTac API: PUT absences/reject.
| Name | Type | Req | Description |
|---|---|---|---|
| absence_id | integer | yes | The absence request id (from timetac_list_absences). |
| comment | string | – | Optional comment shown to the employee. |
No output schema declared.
No examples provided.
timetac_start_time_tracking Start timer ~129
WRITE: start a timer for a user, now or at a given time. Each call can create a new running entry, so do not repeat it. TimeTac API: POST timeTrackings/start.
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | – | – |
| start_time | string | – | Start date-time. Leave empty to start now. |
| start_time_timezone | string | – | IANA time zone of start_time. Needed when start_time is set. |
| task_id | integer | – | The task to book the time on. |
| user_id | integer | yes | The user the timer belongs to. |
No output schema declared.
No examples provided.
timetac_stop_time_tracking Stop timer ~97
WRITE: stop the running timer of a user, now or at a given time. TimeTac API: PUT timeTrackings/stop.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | End date-time. Leave empty to stop now. |
| end_time_timezone | string | yes | IANA time zone, for example Europe/Vienna. |
| notes | string | – | – |
| user_id | integer | yes | The user whose running timer stops. |
No output schema declared.
No examples provided.
How do I install the TimeTac MCP by usefulapi server?
TimeTac MCP by usefulapi is a hosted endpoint at https://timetac.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 · timetac.usefulapi.io
claude mcp add --transport http io-usefulapi-timetac 'https://timetac.usefulapi.io/mcp'
What is the TimeTac MCP by usefulapi server?
TimeTac MCP by usefulapi is listed in the public MCP registry as io.usefulapi/timetac. Read hours, absences and projects; start timers, add entries, approve leave in TimeTac. This page covers its hosted endpoint (https://timetac.usefulapi.io/mcp).
Is the TimeTac MCP by usefulapi server safe to use?
TimeTac MCP by usefulapi scores 18 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 TimeTac MCP by usefulapi server expose?
TimeTac MCP by usefulapi exposes 16 tools: timetac_list_users, timetac_get_user, timetac_list_time_trackings, timetac_current_time_trackings, timetac_list_absences, and 11 more. Their descriptions and schemas cost roughly 1,894 tokens of context every time the server is loaded.
Does the TimeTac MCP by usefulapi server require authentication?
Its publisher declares no required credentials for TimeTac MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the TimeTac MCP by usefulapi server still maintained?
TimeTac MCP by usefulapi 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 did VerifyMCP test on the TimeTac MCP by usefulapi server?
VerifyMCP ran 4 checks on TimeTac MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about TimeTac MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.