io.github.CloudCorpRecords/taskboard-port
NPM · @RENETURCIOS/TASKBOARD-PORT · 2 COMPONENTS
Asana workspaces, projects and tasks via the REST API, as MCP tools.
Available components
Last scanned (2 hours ago)
Scores higher than 31% of npm servers
Category Project Management
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 664 tokens (~60/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- 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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 48
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 npm/@reneturcios/taskboard-port@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_project ~64
Create a new Asana project.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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. |
No output schema declared.
No examples provided.
create_task ~103
Create a new Asana task.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
delete_task ~33
Delete an Asana task.
| Name | Type | Req | Description |
|---|---|---|---|
| task_gid | string | yes | The unique identifier (gid) of the task to delete. |
No output schema declared.
No examples provided.
get_current_user ~16
Get the current Asana user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_project ~36
Get an Asana project by its gid.
| Name | Type | Req | Description |
|---|---|---|---|
| project_gid | string | yes | The unique identifier (gid) of the project to retrieve. |
No output schema declared.
No examples provided.
get_task ~36
Get an Asana task by its gid.
| Name | Type | Req | Description |
|---|---|---|---|
| task_gid | string | yes | The unique identifier (gid) of the task to retrieve. |
No output schema declared.
No examples provided.
list_projects ~49
List Asana projects, optionally within one workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_gid | string | – | Optional unique identifier (gid) of the workspace to list projects from; when omitted, projects across workspaces are listed. |
No output schema declared.
No examples provided.
list_tasks ~110
List Asana tasks by project or assignee, optionally filtered by completion.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_workspaces ~20
List Asana workspaces accessible to the current user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_tasks ~55
Search Asana tasks by text within a workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to search tasks for within the workspace. |
| workspace_gid | string | yes | The unique identifier (gid) of the workspace to search tasks in. |
No output schema declared.
No examples provided.
update_task ~142
Update fields of an existing Asana task.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The unique identifier (gid) of the task to update. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/taskboard-port MCP server?
io.github.CloudCorpRecords/taskboard-port runs locally as an npm package, launched with npx -y @reneturcios/taskboard-port. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/taskboard-port
claude mcp add cloudcorprecords-taskboard-port -- npx -y @reneturcios/taskboard-port
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 npm package (@reneturcios/taskboard-port).
Is the io.github.CloudCorpRecords/taskboard-port MCP server safe to use?
io.github.CloudCorpRecords/taskboard-port scores 63 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. 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.