# io.github.CloudCorpRecords/taskden (oci · ghcr.io/cloudcorprecords/taskden)

DoneBear task workspace over MCP: tasks, projects, checklists, comments and labels.

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

## Components

- npm · `@reneturcios/taskden`: 67/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-taskden/reneturcios-taskden.md), [page](https://verifymcp.io/servers/cloudcorprecords-taskden/reneturcios-taskden)
- oci · `ghcr.io/cloudcorprecords/taskden`: 40/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-taskden/ghcr-io-cloudcorprecords-taskden.md), [page](https://verifymcp.io/servers/cloudcorprecords-taskden/ghcr-io-cloudcorprecords-taskden)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/taskden`
- Version: `0.1.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-21.

- **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**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 6256 tokens (~368/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 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 io.github.CloudCorpRecords/taskden MCP server?

io.github.CloudCorpRecords/taskden runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/taskden:0.1.0 mcp. 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 cloudcorprecords-taskden -- docker run --rm -i ghcr.io/cloudcorprecords/taskden:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-taskden": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/taskden:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-taskden": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/taskden:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-taskden -- docker run --rm -i ghcr.io/cloudcorprecords/taskden:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-taskden": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/taskden:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-taskden:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/taskden:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-taskden": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/taskden:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-taskden": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/taskden:0.1.0",
        "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-20 (score 40, +1)

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

### 2026-11-18 (score 39, +1)

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

### 2026-11-16 (score 38)

First indexed and scored.

## MCP tools (17)

### `guide` (~444 tokens)

Read Guide

Read Done Bear's guide for one topic: what the data means, how it relates to the rest of the product, and how to use it well. Load a topic before doing that kind of work for the first time in a session.

\- `views`: Placing a task in Inbox/Today/Upcoming/Anytime/Someday, reading a view, or working out why Today looks wrong.
\- `dates`: Setting or clearing a due date, or deciding between a deadline and a start date.
\- `editing`: Changing a task's fields, clearing a value, appending to notes, or moving a task between projects.
\- `bulk`: Completing, moving, or editing more than one task at a time, or sweeping a whole view.
\- `checklists`: Adding sub-steps to a task, building a list inside a task, or ticking items off.
\- `comments`: Discussing a task with teammates: reading its thread, replying, or correcting a comment.
\- `projects`: Deciding where a task belongs, creating a project or label, changing a project's status, or joining/leaving a project.
\- `search`: Looking a task up, listing a view, paging through results, or orienting in a new workspace.
\- `workspaces`: Working across multiple workspaces, hitting a permission or rate-limit error, or making retries safe.
\- `agents`: Starting work in a Done Bear workspace for the first time.
\- `importing`: The user asks how to move their tasks in from Todoist, Things, Trello or a CSV.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `topic` (string, required): Guide topic to read

### `get_context` (~337 tokens)

Get Workspace Context

Get a snapshot of the current workspace: task counts per view, recent open tasks, and every project, label, team and member. This is the tool that answers what is in the workspace and resolves a project, label, team or member by name — there is no separate list tool for those. Use it for that, not as a warm-up before every turn. For tasks themselves use task_list (a view), search (by words) or task_show (one task): the recent tasks here are only the latest few.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `projects_status` (string): Which projects to return
- `tasks_limit` (integer): Max recent open tasks to return
- `timezone` (string): IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's…
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `task_list` (~464 tokens)

List Tasks

List tasks in the workspace, most recently updated first. Completed tasks are ordered by completion time, newest first. Filter by view (inbox, today, upcoming, anytime, someday, logbook, trash) and/or state (open, done, archived, all); `search` ranks matches within that filter. `view: "logbook"` reads completed tasks and `view: "trash"` archived ones, whatever `state` says. Returns up to `limit` tasks; `hasMore` is true when more matched than were returned, and passing `nextCursor` back as `cursor` reads the next page. To find a task by its words across every view use search instead, and task_show for one task's checklist, comments and files.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `cursor` (string): Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page.
- `limit` (integer): Max results
- `search` (string): Ranked lexical search over title/description; when set, results are ordered by relevance instead of recency
- `state` (string): Filter by task state
- `timezone` (string): IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's…
- `view` (string): Filter by GTD view bucket. logbook and trash read the completed and archived tasks regardless of `state`
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `task_show` (~324 tokens)

Show Task Details

Get full details for a single task: its fields, labels and checklist items, by workspace-scoped task number. Add `include` for the parts that cost extra reads: `["comments"]` for the discussion thread (oldest first, with author and whether each was edited) and `["attachments"]` for the files on it, each with a short-lived signed URL.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `include` (array): Extra sections to load. Omit unless you need them: each is its own round trip
- `task` (string, required): Workspace-scoped task number, encoded as a string
- `timezone` (string): IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's…
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `task_add` (~657 tokens)

Add Task

Create a new task. An explicit `when` selects its start placement: today, inbox, upcoming, anytime, or someday; upcoming schedules tomorrow. Without `when`, a `deadline` or omitted `timezone` selects anytime first. Otherwise, a `project` or `team` selects inbox; an unfiled task selects today. Pass the user's known IANA `timezone` to resolve calendar days. Use `when: "inbox"` for capture without a commitment to today. `deadline` uses YYYY-MM-DD. Optionally assign the task, attach existing labels, or pass checklist item titles in `checklist`; their order is preserved. The result's `view` reports the selected start placement, while a due or overdue deadline can make the task appear in Today. To change an existing task, use task_edit for fields or the available checklist tools for items. Search first when the user may be describing an existing task.

Input parameters:

- `assignee` (string): Member (user id, name, or email) or task agent (id or name) to assign the task to
- `checklist` (array): Checklist item titles to create on the task, kept in the given order
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `deadline` (string): Due date in YYYY-MM-DD format
- `idempotency_key` (string): Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.
- `labels` (array): Labels to attach (each a label id, title, or id prefix)
- `notes` (string): Task description/notes
- `project` (string): Project id, key, or name to assign this task to
- `team` (string): Team id, key, or name
- `timezone` (string): IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's…
- `title` (string, required): Task title
- `when` (string): GTD view bucket: today, inbox, upcoming, anytime, someday. Omitting this means today, with three exceptions: a deadline or a missing timezone falls back to anytime (the work is due later, or today ca…
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `task_edit` (~609 tokens)

Edit Task

Update fields on one task (`task`) or on several at once (`tasks`, max 50). Only the provided fields are changed; omitted fields are left untouched. To remove a value, list the field in `clear` (e.g. `clear: ["deadline"]`). Notes replace the existing notes (no append). `assignee` assigns the task; clear it to unassign. `add_labels` and `remove_labels` change which labels are on it. Editing several tasks applies the same changes to every one of them and cannot be undone in one call, so confirm the list with the user first. For status changes use task_done, task_reopen or task_archive, and for checklist items use the available checklist tools; this tool does not change either.

Input parameters:

- `add_labels` (array): Labels to attach (each a label id, title, or id prefix). The label has to exist already — create one with label_create
- `assignee` (string): Assign to a member (user id, name, or email) or a task agent (id or name)
- `clear` (array): Fields to remove a value from, e.g. ["deadline"]. Use this rather than sending an empty string.
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `deadline` (string): Set due date (YYYY-MM-DD)
- `notes` (string): New description/notes (replaces existing)
- `project` (string): Project id, key, or name
- `remove_labels` (array): Labels to detach (each a label id, title, or id prefix)
- `task` (string): Workspace-scoped task number, encoded as a string
- `tasks` (array): Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
- `team` (string): Team id, key, or name
- `timezone` (string): IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's…
- `title` (string): New title
- `when` (string): Move to a different GTD view
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `task_agent_get` (~196 tokens)

Read Task Agent Binding

Read the task-agent identity bound to this connection's existing API key in one explicit workspace. Returns only key metadata and the exact agent UUID or null; an inactive agent includes disabledAt. Requires an API-key connection and current workspace membership. Does not register, assign or start any task. Use this before task_agent_register and retain key.id as expected_key_id.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `workspace_id` (string, required)

### `task_agent_register` (~237 tokens)

Register Task Agent Binding

Explicitly register one assignable task agent for this connection's existing key in one workspace, after the user approves that durable binding. Requires a write-scoped API key restricted to exactly this workspace and an owner/admin membership. Read task_agent_get first and pass its key.id as expected_key_id. Same key/workspace/name retries return the same UUID; conflicting or inactive bindings fail without takeover or reactivation. Creates no key, changes no scope, and does not assign/import/start tasks.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `expected_key_id` (string, required)
- `name` (string, required)
- `workspace_id` (string, required)

### `task_done` (~298 tokens)

Complete Task

Mark a task as complete, or several at once with `tasks` (max 50). They move to the Logbook view. A set of 50 is undone one task_reopen call at a time, so confirm the list with the user first.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `expectedRevision` (integer): Complete only the reviewed task revision from task_show or task_list. Use with task, not tasks. A changed task returns a conflict; reload and review before trying again.
- `task` (string): Workspace-scoped task number, encoded as a string
- `tasks` (array): Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `task_reopen` (~232 tokens)

Reopen Task

Reopen a completed task, or several at once with `tasks` (max 50). Each returns to its previous view.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `task` (string): Workspace-scoped task number, encoded as a string
- `tasks` (array): Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `task_archive` (~281 tokens)

Archive Task

Archive a task, or several at once with `tasks` (max 50). They move to the Trash view, out of every working list, and stay readable there (task_list `view: "trash"`). Archiving is not completing: use task_done for work that was finished, and task_archive only for tasks the user wants gone. Confirm with the user first.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `task` (string): Workspace-scoped task number, encoded as a string
- `tasks` (array): Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `project` (~366 tokens)

Manage Project

Create or change a project. `action: "add"` creates one (name required). `action: "edit"` updates the named project: only the fields given change, and an empty string clears description or target_date. `action: "join"` puts it in the caller's Your projects sidebar list and `action: "leave"` takes it out. Read projects with get_context.

Input parameters:

- `action` (string, required): What to do with the project
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `description` (string): Project description (empty string clears it on an edit)
- `idempotency_key` (string): Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.
- `name` (string): Project name. Required on add; a rename on edit
- `project` (string): Project id, key, or name. Required for edit, join and leave
- `status` (string): Project status (edit only)
- `target_date` (string): Target date (YYYY-MM-DD), or an empty string to clear it (edit only)
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `search` (~365 tokens)

Search Tasks

Search tasks across the workspace. Ranked lexical search over title and description: exact and prefix matches rank first, then word-boundary, substring, and fuzzy matches, with recency and status factored in. Multi-word queries match in any order. Searches every state by default, completed and archived included. Use this when the user names a task by its words; use task_list to browse a view (Today, Inbox, …) and task_show once you have the task number.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `cursor` (string): Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page.
- `limit` (integer): Max results
- `query` (string, required): Search query (matches title and description)
- `state` (string): Filter by task state
- `timezone` (string): IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's…
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `checklist` (~405 tokens)

Manage Task Checklist

Change the checklist on a task. `action: "add"` appends items, unchecked, after the existing ones: pass every title for a multi-item list in one call (`titles` keeps the given order, while parallel single adds land in arrival order). `action: "edit"` renames an item and/or checks it (`completed: true`) or unchecks it (`completed: false`). `action: "remove"` deletes one. Read the list, with each item's id and state, from task_show.

Input parameters:

- `action` (string, required): What to do to the checklist
- `completed` (boolean): Check (true) or uncheck (false) the item, on an edit
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `idempotency_key` (string): Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.
- `item` (string): Checklist item UUID or prefix (>= 4 chars). Required to edit or remove
- `task` (string, required): Workspace-scoped task number, encoded as a string
- `title` (string): One item title to add, or the new title on an edit
- `titles` (array): Several item titles to add, kept in the given order (use instead of `title`)
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `comment` (~362 tokens)

Manage Task Comment

Write on a task's comment thread. `action: "add"` posts a comment, attributed to the connected user and visible to everyone in the workspace, so write it as a message to the user's teammates rather than a note to the user; nobody is notified. `action: "edit"` rewrites one of your own (only its author may, and it is then marked edited). `action: "remove"` deletes one permanently — comments have no Trash — so confirm with the user first. Read the thread with task_show and `include: ["comments"]`.

Input parameters:

- `action` (string, required): What to do on the thread
- `body` (string): Comment text. Required to add or edit
- `comment` (string): Comment UUID or prefix (>= 4 chars). Required to edit or remove
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `idempotency_key` (string): Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.
- `task` (string, required): Workspace-scoped task number, encoded as a string
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `attachment` (~410 tokens)

Manage Task Attachment

Add a file to a task or remove one. `action: "add"` fetches the given HTTPS `url`: the server downloads it, verifies its size and type, and stores it, so the model never sends file bytes. Pass a stable idempotency_key and reuse it for retries so a lost response cannot upload the file twice. `action: "remove"` deletes the named `attachment`. Read a task's files with task_show and `include: ["attachments"]`. Limited to 10 attachments per task and 10 MB per file. Allowed types: images (jpeg, png, gif, webp, heic), PDF, CSV, Markdown, and plain text.

Input parameters:

- `action` (string, required): Whether to attach a file or delete one
- `attachment` (string): Attachment UUID or prefix (>= 4 chars). Required to remove
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `filename` (string): Display filename on an add; defaults to the URL's last path segment
- `idempotency_key` (string): Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.
- `task` (string, required): Workspace-scoped task number, encoded as a string
- `url` (string): HTTPS URL of the file to attach. Required to add
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

### `label_create` (~269 tokens)

Create Label

Create a new label in the workspace and return its id. Only creates the label: to put it on a task, pass it to task_add `labels` or task_edit `add_labels` afterwards (both take the title). Titles are not unique, so a second call with the same title makes a duplicate — check the labels get_context returns first, and reuse one that already exists.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `idempotency_key` (string): Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.
- `title` (string, required): Label title
- `workspace` (string): Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-taskden/ghcr-io-cloudcorprecords-taskden#diagnostics

## Score history

- 2026-11-21: 40
- 2026-11-20: 40
- 2026-11-19: 39
- 2026-11-18: 39
- 2026-11-17: 38
- 2026-11-16: 38

## Common questions

### What is the io.github.CloudCorpRecords/taskden MCP server?

io.github.CloudCorpRecords/taskden is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/taskden. DoneBear task workspace over MCP: tasks, projects, checklists, comments and labels. This page covers its container image (ghcr.io/cloudcorprecords/taskden).

### Is the io.github.CloudCorpRecords/taskden MCP server safe to use?

io.github.CloudCorpRecords/taskden scores 40 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 io.github.CloudCorpRecords/taskden MCP server expose?

io.github.CloudCorpRecords/taskden exposes 17 tools: guide, get_context, task_list, task_show, task_add, and 12 more. Their descriptions and schemas cost roughly 6,256 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/taskden MCP server still maintained?

io.github.CloudCorpRecords/taskden is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.CloudCorpRecords/taskden MCP server under?

io.github.CloudCorpRecords/taskden 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 io.github.CloudCorpRecords/taskden MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/taskden, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/taskden: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/taskden
- Repository: https://github.com/CloudCorpRecords/taskden
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-taskden/ghcr-io-cloudcorprecords-taskden.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-taskden/ghcr-io-cloudcorprecords-taskden/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-taskden/ghcr-io-cloudcorprecords-taskden.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-taskden/ghcr-io-cloudcorprecords-taskden
