io.github.CloudCorpRecords/tasklist-port
NPM · @RENETURCIOS/TASKLIST-PORT · 2 COMPONENTS
Todoist tasks, projects, labels and sections as MCP tools.
Available components
Last scanned (5 hours ago)
Scores higher than 31% of npm servers
Category Productivity and Notes
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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 549 tokens (~45/item across 12 items; 12 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 12 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/tasklist-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 →
close_task ~39
Close (complete) a Todoist task by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The unique identifier of the Todoist task to close (complete). |
No output schema declared.
No examples provided.
create_project ~42
Create a Todoist project.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Optional color name for the new project. |
| name | string | yes | The name to give the new project. |
No output schema declared.
No examples provided.
create_task ~100
Create a Todoist task.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text content of the new task. |
| due_string | string | – | Optional due date for the task in Todoist's natural-language due string format. |
| labels | array | – | Optional list of label names to apply to the new task. |
| priority | number | – | Optional priority level for the task. |
| project_id | string | – | Optional identifier of the project to create the task in. |
No output schema declared.
No examples provided.
delete_task ~34
Delete a Todoist task by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The unique identifier of the Todoist task to delete. |
No output schema declared.
No examples provided.
get_project ~35
Retrieve a single Todoist project by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The unique identifier of the Todoist project to retrieve. |
No output schema declared.
No examples provided.
get_task ~35
Retrieve a single Todoist task by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The unique identifier of the Todoist task to retrieve. |
No output schema declared.
No examples provided.
list_labels ~13
List Todoist labels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects ~13
List Todoist projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sections ~36
List Todoist sections for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The unique identifier of the Todoist project whose sections to list. |
No output schema declared.
No examples provided.
list_tasks ~79
List Todoist tasks, optionally filtered by project, label, or filter query.
| Name | Type | Req | Description |
|---|---|---|---|
| filter_query | string | – | Optional Todoist filter query, sent as the filter parameter, to filter tasks by. |
| label | string | – | Optional label name to filter tasks by. |
| project_id | string | – | Optional identifier of the project to list tasks from. |
No output schema declared.
No examples provided.
reopen_task ~37
Reopen a completed Todoist task by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The unique identifier of the completed Todoist task to reopen. |
No output schema declared.
No examples provided.
update_task ~86
Update a Todoist task by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Optional new text content for the task. |
| due_string | string | – | Optional new due date for the task in Todoist's natural-language due string format. |
| priority | number | – | Optional new priority level for the task. |
| task_id | string | yes | The unique identifier of the Todoist task to update. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/tasklist-port MCP server?
io.github.CloudCorpRecords/tasklist-port runs locally as an npm package, launched with npx -y @reneturcios/tasklist-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/tasklist-port
claude mcp add cloudcorprecords-tasklist-port -- npx -y @reneturcios/tasklist-port
What is the io.github.CloudCorpRecords/tasklist-port MCP server?
io.github.CloudCorpRecords/tasklist-port is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/tasklist-port. Todoist tasks, projects, labels and sections as MCP tools. This page covers its npm package (@reneturcios/tasklist-port).
Is the io.github.CloudCorpRecords/tasklist-port MCP server safe to use?
io.github.CloudCorpRecords/tasklist-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/tasklist-port MCP server expose?
io.github.CloudCorpRecords/tasklist-port exposes 12 tools: list_tasks, get_task, create_task, update_task, close_task, and 7 more. Their descriptions and schemas cost roughly 549 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/tasklist-port MCP server still maintained?
io.github.CloudCorpRecords/tasklist-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/tasklist-port MCP server under?
io.github.CloudCorpRecords/tasklist-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.