Petodo
NPM · PETODO-CLI
Your Petodo to-do list for AI assistants: list, add, complete, edit and report on tasks.
Available components
Last scanned (17 hours ago)
Scores higher than 40% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 393 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- Stability: unverified → 0.10 ▲ functional
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Nov 26 50
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 21 Nov 2026 · Analysed npm/petodo-cli@1.1.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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
add_task ~169
Add a task. Times written in plain language inside the title are understood: "call Sam 2pm" schedules itself for 2pm and the user is reminded beforehand. So are repeats: "gym every weekday at 6pm" sets up a repeating task, which appears one day at a time. Pass dueAt or repeat only to override what the title says.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | – |
| dueAt | string | – | ISO-8601 time, if you need to be explicit. |
| repeat | object | – | Makes this a repeating task. Usually unnecessary: a title like "gym every weekday at 6pm" is read for you. Pass this only to be explicit. |
| title | string | yes | What to do, e.g. "call Sam 2pm". |
No output schema declared.
No examples provided.
complete_task ~34
Mark a task done, or reopen it.
| Name | Type | Req | Description |
|---|---|---|---|
| done | boolean | – | Defaults to true. |
| id | string | yes | – |
No output schema declared.
No examples provided.
delete_task ~20
Delete a task permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_report ~49
A summary of the user's list: counts, what is overdue, what is due within the hour, and their streak. Includes snapshotAgeSeconds; if it is large, say the data may be stale.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tasks ~62
List the user's Petodo tasks. Returns each task's id, title, whether it is done, its day and its due time, plus any repeating rules behind them.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | Defaults to all. |
| status | string | – | Defaults to open. |
No output schema declared.
No examples provided.
update_task ~59
Change a task's title, due time or day. Pass dueAt as null to clear the time.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | – |
| dueAt | string|null | – | – |
| id | string | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the Petodo MCP server?
Petodo runs locally as an npm package, launched with npx -y petodo-cli mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · petodo-cli
claude mcp add gaby3637-petodo -- npx -y petodo-cli mcp
What is the Petodo MCP server?
Petodo is an MCP server listed in the public MCP registry as io.github.gaby3637/petodo. Your Petodo to-do list for AI assistants: list, add, complete, edit and report on tasks. This page covers its npm package (petodo-cli).
Is the Petodo MCP server safe to use?
Petodo scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Petodo MCP server expose?
Petodo exposes 6 tools: list_tasks, add_task, complete_task, update_task, delete_task, get_report. Their descriptions and schemas cost roughly 393 tokens of context every time the server is loaded.
Is the Petodo MCP server still maintained?
Petodo 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 Petodo MCP server under?
Petodo 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 Petodo MCP server?
VerifyMCP ran 16 checks on Petodo, 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.