io.github.rog0x/task
NPM · @ROG0X/MCP-TASK-TOOLS
Todo, priority, estimation, burndown for AI agents
Available components
Last scanned (8 hours ago)
Scores higher than 75% 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 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 228 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 557 tokens (~111/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-task-tools@1.0.1
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 →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
burndown_calculator ~100
Calculate sprint burndown chart data. Given tasks with story points and sprint duration, computes ideal vs actual burndown, velocity metrics, and completion forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| current_day | number | yes | Current day of the sprint (0-indexed) |
| sprint_duration_days | number | yes | Total sprint duration in days |
| sprint_name | string | – | Name of the sprint |
| tasks | array | yes | Sprint tasks with points and completion data |
No output schema declared.
No examples provided.
priority_sorter ~112
Sort and prioritize tasks using proven frameworks: Eisenhower matrix (urgent/important quadrants), RICE scoring (reach, impact, confidence, effort), or MoSCoW method (must/should/could/wont).
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | Prioritization framework to use |
| tasks | array | yes | Tasks to prioritize. Fields depend on method: eisenhower needs urgent/important booleans; rice needs reach/impact/confidence/effort numbers; moscow needs moscow category string. |
No output schema declared.
No examples provided.
standup_generator ~63
Generate a daily standup update from the current task list. Shows yesterday (recently completed), today (in progress), and blockers. Uses data from todo_manager.
| Name | Type | Req | Description |
|---|---|---|---|
| lookback_hours | number | – | Hours to look back for completed tasks (default: 24) |
No output schema declared.
No examples provided.
time_estimator ~106
Estimate task duration using PERT methodology. Break a task into subtasks, provide optimistic/realistic/pessimistic estimates for each. Returns weighted expected time plus configurable buffer.
| Name | Type | Req | Description |
|---|---|---|---|
| buffer_percent | number | – | Buffer percentage to add (default: 20) |
| subtasks | array | yes | Subtasks with time estimates |
| task | string | yes | Name of the overall task |
| unit | string | – | Time unit: hours, days, weeks (default: hours) |
No output schema declared.
No examples provided.
todo_manager ~176
Manage an in-memory task list. Add, complete, update status, delete, and list tasks. Supports filtering by status, priority, and tags. Persistent within session.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform on the task list |
| description | string | – | Task description (optional, for add) |
| id | string | – | Task ID (required for complete, update_status, delete) |
| points | number | – | Story points for the task (default: 1) |
| priority | string | – | Task priority (for add or list filter) |
| status | string | – | Task status (for update_status or list filter) |
| tag | string | – | Filter by tag (for list) |
| tags | array | – | Tags for the task (for add) |
| title | string | – | Task title (required for add) |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/task MCP server?
io.github.rog0x/task runs locally as an npm package, launched with npx -y @rog0x/mcp-task-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-task-tools
claude mcp add rog0x-task -- npx -y @rog0x/mcp-task-tools
What is the io.github.rog0x/task MCP server?
io.github.rog0x/task is an MCP server listed in the public MCP registry as io.github.rog0x/task. Todo, priority, estimation, burndown for AI agents. This page covers its npm package (@rog0x/mcp-task-tools).
Is the io.github.rog0x/task MCP server safe to use?
io.github.rog0x/task scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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.rog0x/task MCP server expose?
io.github.rog0x/task exposes 5 tools: todo_manager, priority_sorter, time_estimator, standup_generator, burndown_calculator. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.
Is the io.github.rog0x/task MCP server still maintained?
io.github.rog0x/task is still listed as active in the MCP registry. We last reached this channel on 6 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.rog0x/task MCP server under?
io.github.rog0x/task 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.rog0x/task MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/task, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.