Time Doctor
OCI · GHCR.IO/WYRE-AI/TIMEDOCTOR-MCP
MCP server for Time Doctor's employee time-tracking API — companies, users, projects, and stats.
Available components
Last scanned (6 hours ago)
Scores higher than 38% of OCI servers
Category Productivity and Notes
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 811 tokens (~73/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 37
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 · Analysed oci/ghcr.io/wyre-ai/timedoctor-mcp@v1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
timedoctor_check_invitation ~55
Check whether a Time Doctor company invitation exists for an email address (read-only - does not send or manage invitations).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company ID. |
| string | yes | Email address to check. |
No output schema declared.
No examples provided.
timedoctor_get_company ~30
Get a single Time Doctor company by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | Company ID. |
No output schema declared.
No examples provided.
timedoctor_get_project ~39
Get a single Time Doctor project by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company ID. |
| projectId | string | yes | Project ID. |
No output schema declared.
No examples provided.
timedoctor_get_task ~39
Get a single Time Doctor task by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company ID. |
| taskId | string | yes | Task ID. |
No output schema declared.
No examples provided.
timedoctor_get_timeuse_stats ~139
Get aggregated Time Doctor productivity statistics (time spent per application/category, productive vs. unproductive) for a user or company within a time range.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category to fetch the report for. |
| company | string | yes | Company ID. |
| from | string | – | ISO 8601 start of range (inclusive). |
| limit | string | – | Maximum number of results to return. |
| page | string | – | Number of results to skip. |
| to | string | – | ISO 8601 end of range (exclusive). |
| user | string | – | Comma-separated user IDs. Defaults to the authenticated user. |
No output schema declared.
No examples provided.
timedoctor_get_user ~43
Get a single Time Doctor user by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company ID the user belongs to. |
| userId | string | yes | User ID. |
No output schema declared.
No examples provided.
timedoctor_get_worklog ~129
Get detailed Time Doctor work-session log (start times, duration, task/project, mode) for a user or company within a time range. For best performance, query <=7-day windows at a time.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company ID. |
| from | string | – | ISO 8601 start of range (inclusive). |
| taskProjectNames | boolean | – | Resolve task/project names instead of only IDs. |
| to | string | – | ISO 8601 end of range (exclusive). |
| user | string | – | Comma-separated user IDs. Defaults to the authenticated user. |
No output schema declared.
No examples provided.
timedoctor_list_companies ~28
List Time Doctor companies (workspaces) the authenticated user owns or administers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timedoctor_list_projects ~86
List Time Doctor projects in a company.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Return all company projects instead of only ones assigned to the caller. |
| company | string | yes | Company ID. |
| limit | string | – | Maximum number of results to return. |
| name | string | – | Filter: name starts with this value. |
| page | string | – | Number of results to skip. |
No output schema declared.
No examples provided.
timedoctor_list_tasks ~106
List Time Doctor tasks in a company, optionally filtered by project, name, or open/closed status.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company ID. |
| limit | string | – | Maximum number of results to return. |
| name | string | – | Filter: name starts with this value. |
| page | string | – | Number of results to skip. |
| projects | string | – | Comma-separated project IDs to filter by. |
| status | string | – | Filter by task status. |
No output schema declared.
No examples provided.
timedoctor_list_users ~117
List Time Doctor users, optionally scoped to a company and filtered by email/name.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company ID. If omitted, scope is global to the authenticated user. |
| string | – | Filter: email starts with this value. | |
| includeArchivedUsers | boolean | – | Include archived (hidden by default) users. |
| limit | string | – | Maximum number of results to return. |
| name | string | – | Filter: name starts with this value. |
| page | string | – | Number of results to skip. |
No output schema declared.
No examples provided.
How do I install the Time Doctor MCP server?
Time Doctor runs locally as a container image, launched with docker run --rm -i -e TIMEDOCTOR_EMAIL -e TIMEDOCTOR_PASSWORD -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/timedoctor-mcp:v1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-ai/timedoctor-mcp
claude mcp add wyre-ai-timedoctor-mcp -- docker run --rm -i -e TIMEDOCTOR_EMAIL -e TIMEDOCTOR_PASSWORD -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/timedoctor-mcp:v1.0.3
This image reads TIMEDOCTOR_EMAIL, TIMEDOCTOR_PASSWORD, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Time Doctor MCP server?
Time Doctor is an MCP server listed in the public MCP registry as io.github.WYRE-AI/timedoctor-mcp. MCP server for Time Doctor's employee time-tracking API, companies, users, projects, and stats. This page covers its container image (ghcr.io/wyre-ai/timedoctor-mcp).
Is the Time Doctor MCP server safe to use?
Time Doctor scores 38 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 Time Doctor MCP server expose?
Time Doctor exposes 11 tools: timedoctor_list_companies, timedoctor_get_company, timedoctor_list_users, timedoctor_get_user, timedoctor_check_invitation, and 6 more. Their descriptions and schemas cost roughly 811 tokens of context every time the server is loaded.
Is the Time Doctor MCP server still maintained?
Time Doctor 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 Time Doctor MCP server under?
Time Doctor declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.