# Time Doctor (oci · ghcr.io/wyre-ai/timedoctor-mcp)

MCP server for Time Doctor's employee time-tracking API — companies, users, projects, and stats.

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/wyre-ai/timedoctor-mcp`: 38/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-timedoctor-mcp/ghcr-io-wyre-ai-timedoctor-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-timedoctor-mcp/ghcr-io-wyre-ai-timedoctor-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/timedoctor-mcp`
- Version: `v1.0.3`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 811 tokens (~73/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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).
  - 100% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
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.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-timedoctor-mcp": {
      "command": "docker",
      "args": [
        "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.

### VS Code

```json
{
  "servers": {
    "wyre-ai-timedoctor-mcp": {
      "command": "docker",
      "args": [
        "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.

### Codex

```bash
codex 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-timedoctor-mcp": {
      "type": "local",
      "command": [
        "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"
      ],
      "enabled": true
    }
  }
}
```

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.

### Hermes

```yaml
mcp_servers:
  wyre-ai-timedoctor-mcp:
    command: "docker"
    args: ["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.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-timedoctor-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "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.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-timedoctor-mcp": {
      "command": "docker",
      "args": [
        "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.

## 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-11-04 (score 38, +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.

### 2026-11-03 (score 37)

First indexed and scored.

## MCP tools (11)

### `timedoctor_list_companies` (~28 tokens)

List Time Doctor companies (workspaces) the authenticated user owns or administers.

### `timedoctor_get_company` (~30 tokens)

Get a single Time Doctor company by ID.

Input parameters:

- `companyId` (string, required): Company ID.

### `timedoctor_list_users` (~117 tokens)

List Time Doctor users, optionally scoped to a company and filtered by email/name.

Input parameters:

- `company` (string): Company ID. If omitted, scope is global to the authenticated user.
- `email` (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.

### `timedoctor_get_user` (~43 tokens)

Get a single Time Doctor user by ID.

Input parameters:

- `company` (string): Company ID the user belongs to.
- `userId` (string, required): User ID.

### `timedoctor_check_invitation` (~55 tokens)

Check whether a Time Doctor company invitation exists for an email address (read-only - does not send or manage invitations).

Input parameters:

- `company` (string, required): Company ID.
- `email` (string, required): Email address to check.

### `timedoctor_list_projects` (~86 tokens)

List Time Doctor projects in a company.

Input parameters:

- `all` (boolean): Return all company projects instead of only ones assigned to the caller.
- `company` (string, required): 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.

### `timedoctor_get_project` (~39 tokens)

Get a single Time Doctor project by ID.

Input parameters:

- `company` (string, required): Company ID.
- `projectId` (string, required): Project ID.

### `timedoctor_list_tasks` (~106 tokens)

List Time Doctor tasks in a company, optionally filtered by project, name, or open/closed status.

Input parameters:

- `company` (string, required): 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.

### `timedoctor_get_task` (~39 tokens)

Get a single Time Doctor task by ID.

Input parameters:

- `company` (string, required): Company ID.
- `taskId` (string, required): Task ID.

### `timedoctor_get_worklog` (~129 tokens)

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.

Input parameters:

- `company` (string, required): 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.

### `timedoctor_get_timeuse_stats` (~139 tokens)

Get aggregated Time Doctor productivity statistics (time spent per application/category, productive vs. unproductive) for a user or company within a time range.

Input parameters:

- `category` (string): Category to fetch the report for.
- `company` (string, required): 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.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-timedoctor-mcp/ghcr-io-wyre-ai-timedoctor-mcp#diagnostics

## Score history

- 2026-11-05: 38
- 2026-11-04: 38
- 2026-11-03: 37

## Common questions

### 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.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/timedoctor-mcp
- Repository: https://github.com/WYRE-AI/timedoctor-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-timedoctor-mcp/ghcr-io-wyre-ai-timedoctor-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-timedoctor-mcp/ghcr-io-wyre-ai-timedoctor-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-timedoctor-mcp/ghcr-io-wyre-ai-timedoctor-mcp