# com.pyunto/time-management (npm · @pyunto/tm-mcp)

Read your Pyunto Time Management schedule and log time from an AI assistant. E2EE project planning.

- Trust score: 83/100 (high trust)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@pyunto/tm-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-pyunto-time-management/pyunto-tm-mcp.md), [page](https://verifymcp.io/servers/com-pyunto-time-management/pyunto-tm-mcp)

## Channel facts

- Registry: `npm`
- Package: `@pyunto/tm-mcp`
- Version: `0.4.0`
- 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**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pyunto/tm-integrations).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1684 tokens (~120/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_time_block" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 14 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.

## Install

### How do I install the com.pyunto/time-management MCP server?

com.pyunto/time-management runs locally as an npm package, launched with npx -y @pyunto/tm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-pyunto-time-management -- npx -y @pyunto/tm-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-pyunto-time-management": {
      "command": "npx",
      "args": [
        "-y",
        "@pyunto/tm-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-pyunto-time-management": {
      "command": "npx",
      "args": [
        "-y",
        "@pyunto/tm-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-pyunto-time-management -- npx -y @pyunto/tm-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pyunto-time-management": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pyunto/tm-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pyunto-time-management --command npx --arg -y --arg @pyunto/tm-mcp
```

### Hermes

```yaml
mcp_servers:
  com-pyunto-time-management:
    command: "npx"
    args: ["-y", "@pyunto/tm-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-pyunto-time-management": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pyunto/tm-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-pyunto-time-management -t stdio -c npx -a -y @pyunto/tm-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-pyunto-time-management": {
      "command": "npx",
      "args": [
        "-y",
        "@pyunto/tm-mcp"
      ]
    }
  }
}
```

## 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-05 (score 83, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +6)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Schema quality: 1113 → 1684
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.47
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.3.6 → 0.4.0

### 2026-10-24 (score 75, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-18 (score 80, +31)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 0
- [functional] First check of Tool coverage: 100
- [functional] Package version: 0.3.5 → 0.3.6

### 2026-10-12 (score 49, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-11 (score 49, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-09-30 (score 0)

- [security improvement] Malware scan: unverified → pass

## MCP tools (14)

### `whoami` (~56 tokens)

Who this MCP server is connected as: account email, API key name, granted scopes, server URL, and whether end-to-end-encrypted names can be decrypted. Call this first when a tool fails, to see which scopes are missing.

### `list_projects` (~55 tokens)

List every project the account can see, with id, name, colour and role (owner/editor/viewer). Use it to resolve a project name the user typed into the project_id other tools need. Requires the projects:read scope.

### `list_tasks` (~93 tokens)

List Gantt tasks (and subtasks) with their id, project, name and date range. Filter to one project with project_id. Use it to resolve a task name into the task_id that log_time takes. Requires the projects:read scope.

Input parameters:

- `active_on` (string): YYYY-MM-DD — keep only tasks whose date range covers this day.
- `project_id` (number): Only tasks in this project.

### `list_time_blocks` (~84 tokens)

The individual time blocks logged between two dates (inclusive, max 92 days), with start/end times, duration, project, task and memo. This is the detailed schedule; use time_summary when you only need totals. Requires blocks:read.

Input parameters:

- `date_from` (string, required): YYYY-MM-DD (inclusive).
- `date_to` (string, required): YYYY-MM-DD (inclusive).

### `time_summary` (~107 tokens)

Total hours logged between two dates (inclusive, max 92 days), grouped by project, by task, or by day. This is the tool to answer 'how much time did I spend on X' and to write a work log or diary entry. Requires record:read.

Input parameters:

- `date_from` (string, required): YYYY-MM-DD (inclusive).
- `date_to` (string, required): YYYY-MM-DD (inclusive).
- `group_by` (string): Grouping for the totals. Default: project.

### `log_time` (~163 tokens)

Record a block of worked time on the calendar. Writes to the user's real schedule, so confirm the project, date and times with them before calling it. Requires the blocks:write scope; for an end-to-end-encrypted project a memo additionally needs PYUNTO_TM_PASSWORD so it can be encrypted locally.

Input parameters:

- `date` (string, required): YYYY-MM-DD.
- `end` (string, required): "HH:MM" (24h) or minutes past midnight.
- `memo` (string): What was worked on. Encrypted client-side.
- `project_id` (number, required): From list_projects.
- `start` (string, required): "HH:MM" (24h) or minutes past midnight.
- `task_id` (number): Gantt task to attribute the time to.

### `update_time_block` (~222 tokens)

Change an already-recorded time block: its date, start/end times, memo, or the task it counts towards. Get block_id from list_time_blocks. Only the fields you pass change. Tell the user what the block currently says and what it will say before calling this. Requires the blocks:write scope; changing a memo on an end-to-end-encrypted project also needs PYUNTO_TM_PASSWORD, and project_id so the memo is encrypted under the right key.

Input parameters:

- `block_id` (number, required): From list_time_blocks.
- `date` (string): YYYY-MM-DD.
- `end` (string): "HH:MM" (24h) or minutes past midnight.
- `memo` (string): Replaces the memo. Needs project_id.
- `project_id` (number): The block's project, from list_time_blocks. Required with memo.
- `start` (string): "HH:MM" (24h) or minutes past midnight.
- `task_id` (number): Task to attribute the time to; 0 detaches it.

### `delete_time_block` (~189 tokens)

Permanently delete ONE recorded time block, along with any files attached to it. Before calling it you MUST show the user the block you are about to delete (date, start and end time, project, task and memo, from list_time_blocks) and get an explicit yes for that specific block. Never infer the block from a vague instruction, and never delete several blocks because the user described a range — confirm and delete them one at a time. A deleted block can be put back with restore_time_block for 14 days, after which it and its attachments are purged for good and cannot be recovered; say so when you report the deletion, and do not tell the user the deletion is irreversible. Requires the blocks:delete scope, which is separate from blocks:write and has to be granted deliberately.

Input parameters:

- `block_id` (number, required): From list_time_blocks. Exactly one block is deleted.

### `list_deleted_time_blocks` (~67 tokens)

Time blocks that were deleted but can still be restored, newest first, each with the date it was deleted and the deadline for putting it back. Use it to find the block_id for restore_time_block when the user says they deleted something by mistake. Requires the blocks:read scope.

### `restore_time_block` (~77 tokens)

Put a deleted time block back on the calendar, along with any files that were attached to it. Get block_id from list_deleted_time_blocks. Works only within the 14-day recovery window; after that the block is gone for good. Requires the blocks:write scope.

Input parameters:

- `block_id` (number, required): From list_deleted_time_blocks.

### `create_task` (~183 tokens)

Add a task to the Gantt chart — a piece of work with a start and end date, which is what time blocks are later logged against. Use this for work that spans days or longer; for time already worked use log_time instead. Writes to the user's real plan, so confirm the project, name and dates with them first. Requires the tasks:write scope; an end-to-end-encrypted project also needs PYUNTO_TM_PASSWORD so the name can be encrypted locally.

Input parameters:

- `end_date` (string, required): YYYY-MM-DD, inclusive. May be years out.
- `name` (string, required): What the task is. Encrypted client-side.
- `parent_task_id` (number): Make this a subtask of that task, in the same project.
- `project_id` (number, required): From list_projects.
- `start_date` (string, required): YYYY-MM-DD.

### `complete_task` (~92 tokens)

Mark a Gantt task finished, or reopen it. The task stays on the chart, drawn dimmed — nothing is deleted. This is how a finished piece of work shows up on the plan. Get task_id from list_tasks. Requires the tasks:write scope.

Input parameters:

- `completed` (boolean): true marks it done (the default), false reopens it.
- `task_id` (number, required): From list_tasks.

### `update_task` (~185 tokens)

Change a task's name, dates, or whether it is archived. Only the fields you pass change. Moving the dates also moves every task that depends on this one, and the reply lists everything that moved — tell the user about those too. Archiving hides a task from every view and is reversible; there is deliberately no way to delete a task through this server, because that would detach the time already logged against it. Requires the tasks:write scope; renaming an end-to-end-encrypted project's task also needs PYUNTO_TM_PASSWORD.

Input parameters:

- `archived` (boolean): true hides it from every view (reversible), false brings it back.
- `end_date` (string): YYYY-MM-DD, inclusive.
- `name` (string): Replaces the name.
- `start_date` (string): YYYY-MM-DD.
- `task_id` (number, required): From list_tasks.

### `set_monthly_target` (~111 tokens)

Set how many hours a task should get in one calendar month. This is what the daily draft (the ✨ button) divides across the month's remaining workdays — a task with no target is skipped entirely, which is the usual reason the draft produces nothing. Requires the tasks:write scope.

Input parameters:

- `hours` (number, required): Target hours for that month. 0 clears it.
- `task_id` (number, required): From list_tasks.
- `year_month` (string, required): Calendar month, "YYYY-MM".

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-pyunto-time-management/pyunto-tm-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 80
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 49
- 2026-10-16: 49
- 2026-10-15: 49
- 2026-10-14: 49
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-11: 49
- 2026-10-04: 49
- 2026-10-03: 49
- 2026-10-02: 49
- 2026-10-01: 49

## Common questions

### What is the com.pyunto/time-management MCP server?

com.pyunto/time-management is an MCP server listed in the public MCP registry as com.pyunto/time-management. Read your Pyunto Time Management schedule and log time from an AI assistant. E2EE project planning. This page covers its npm package (@pyunto/tm-mcp).

### Is the com.pyunto/time-management MCP server safe to use?

com.pyunto/time-management scores 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 com.pyunto/time-management MCP server expose?

com.pyunto/time-management exposes 14 tools: whoami, list_projects, list_tasks, list_time_blocks, time_summary, and 9 more. Their descriptions and schemas cost roughly 1,684 tokens of context every time the server is loaded.

### Is the com.pyunto/time-management MCP server still maintained?

com.pyunto/time-management 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 com.pyunto/time-management MCP server under?

com.pyunto/time-management declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the com.pyunto/time-management MCP server?

VerifyMCP ran 15 checks on com.pyunto/time-management, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about com.pyunto/time-management: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pyunto/tm-mcp
- Socket report: https://socket.dev/npm/package/@pyunto/tm-mcp
- Repository: https://github.com/pyunto/tm-integrations
- Website: https://tm.pyunto.com/docs/mcp.en.md
- Changelog RSS feed: https://verifymcp.io/servers/com-pyunto-time-management/pyunto-tm-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pyunto-time-management/pyunto-tm-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-pyunto-time-management/pyunto-tm-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-pyunto-time-management/pyunto-tm-mcp