# io.github.CloudCorpRecords/taskboard-port (oci · ghcr.io/cloudcorprecords/taskboard-port)

Asana workspaces, projects and tasks via the REST API, as MCP tools.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/taskboard-port`
- 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-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**: 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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 664 tokens (~60/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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_task" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - 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 io.github.CloudCorpRecords/taskboard-port MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-taskboard-port": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/taskboard-port: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-04 (score 40, +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-03 (score 39, 0)

- [security regression] Provenance: unverified → fail

### 2026-11-02 (score 39)

First indexed and scored.

## MCP tools (11)

### `get_current_user` (~16 tokens)

Get the current Asana user.

### `list_workspaces` (~20 tokens)

List Asana workspaces accessible to the current user.

### `list_projects` (~49 tokens)

List Asana projects, optionally within one workspace.

Input parameters:

- `workspace_gid` (string): Optional unique identifier (gid) of the workspace to list projects from; when omitted, projects across workspaces are listed.

### `get_project` (~36 tokens)

Get an Asana project by its gid.

Input parameters:

- `project_gid` (string, required): The unique identifier (gid) of the project to retrieve.

### `create_project` (~64 tokens)

Create a new Asana project.

Input parameters:

- `name` (string, required): The name of the new project.
- `notes` (string): Optional notes describing the new project.
- `workspace_gid` (string): Optional unique identifier (gid) of the workspace in which to create the project.

### `list_tasks` (~110 tokens)

List Asana tasks by project or assignee, optionally filtered by completion.

Input parameters:

- `assignee_gid` (string): Optional unique identifier (gid) of the user whose assigned tasks to list, used when no project_gid is given.
- `completed` (boolean): Optional completion filter applied client-side: true returns only completed tasks, false only incomplete tasks.
- `project_gid` (string): Optional unique identifier (gid) of the project whose tasks to list; takes precedence over assignee_gid when both are given.

### `get_task` (~36 tokens)

Get an Asana task by its gid.

Input parameters:

- `task_gid` (string, required): The unique identifier (gid) of the task to retrieve.

### `create_task` (~103 tokens)

Create a new Asana task.

Input parameters:

- `assignee_gid` (string): Optional unique identifier (gid) of the user to assign the new task to.
- `due_on` (string): Optional due date for the task, in YYYY-MM-DD format.
- `name` (string, required): The name of the new task.
- `notes` (string): Optional notes describing the new task.
- `projects` (array): Optional array of project gids to add the new task to.

### `update_task` (~142 tokens)

Update fields of an existing Asana task.

Input parameters:

- `assignee_gid` (string): Optional unique identifier (gid) of the user to reassign the task to.
- `completed` (boolean): Optional completion state to set: true marks the task completed, false marks it incomplete.
- `due_on` (string): Optional new due date for the task, in YYYY-MM-DD format.
- `name` (string): Optional new name for the task; omitted fields are left unchanged.
- `notes` (string): Optional new notes for the task; omitted fields are left unchanged.
- `task_gid` (string, required): The unique identifier (gid) of the task to update.

### `delete_task` (~33 tokens)

Delete an Asana task.

Input parameters:

- `task_gid` (string, required): The unique identifier (gid) of the task to delete.

### `search_tasks` (~55 tokens)

Search Asana tasks by text within a workspace.

Input parameters:

- `text` (string, required): The text to search tasks for within the workspace.
- `workspace_gid` (string, required): The unique identifier (gid) of the workspace to search tasks in.

## Diagnostics

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

## Score history

- 2026-11-05: 40
- 2026-11-04: 40
- 2026-11-03: 39
- 2026-11-02: 39

## Common questions

### What is the io.github.CloudCorpRecords/taskboard-port MCP server?

io.github.CloudCorpRecords/taskboard-port is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/taskboard-port. Asana workspaces, projects and tasks via the REST API, as MCP tools. This page covers its container image (ghcr.io/cloudcorprecords/taskboard-port).

### Is the io.github.CloudCorpRecords/taskboard-port MCP server safe to use?

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

io.github.CloudCorpRecords/taskboard-port exposes 11 tools: get_current_user, list_workspaces, list_projects, get_project, create_project, and 6 more. Their descriptions and schemas cost roughly 664 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/taskboard-port MCP server still maintained?

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

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

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/taskboard-port, 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/taskboard-port: 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/taskboard-port
- Repository: https://github.com/CloudCorpRecords/taskboard-port
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-taskboard-port/ghcr-io-cloudcorprecords-taskboard-port.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-taskboard-port/ghcr-io-cloudcorprecords-taskboard-port/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-taskboard-port/ghcr-io-cloudcorprecords-taskboard-port.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-taskboard-port/ghcr-io-cloudcorprecords-taskboard-port
