# Petodo (npm · petodo-cli)

Your Petodo to-do list for AI assistants: list, add, complete, edit and report on tasks.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `petodo-cli`: 69/100 (this document), [markdown](https://verifymcp.io/servers/gaby3637-petodo/petodo-cli.md), [page](https://verifymcp.io/servers/gaby3637-petodo/petodo-cli)

## Channel facts

- Registry: `npm`
- Package: `petodo-cli`
- Version: `1.1.1`
- 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-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **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 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 393 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 46% 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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add gaby3637-petodo -- npx -y petodo-cli mcp
```

### Cursor

```json
{
  "mcpServers": {
    "gaby3637-petodo": {
      "command": "npx",
      "args": [
        "-y",
        "petodo-cli",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gaby3637-petodo": {
      "command": "npx",
      "args": [
        "-y",
        "petodo-cli",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add gaby3637-petodo -- npx -y petodo-cli mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gaby3637-petodo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "petodo-cli",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gaby3637-petodo --command npx --arg -y --arg petodo-cli --arg mcp
```

### Hermes

```yaml
mcp_servers:
  gaby3637-petodo:
    command: "npx"
    args: ["-y", "petodo-cli", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "gaby3637-petodo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "petodo-cli",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add gaby3637-petodo -t stdio -c npx -a -y petodo-cli mcp
```

### Other

```json
{
  "mcpServers": {
    "gaby3637-petodo": {
      "command": "npx",
      "args": [
        "-y",
        "petodo-cli",
        "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-20 (score 69, +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.

### 2026-11-18 (score 68, +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.

### 2026-11-16 (score 67, +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.

### 2026-11-14 (score 66, +1)

- [functional improvement] Stability: unverified → 0.10

### 2026-11-12 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-11 (score 50)

First indexed and scored.

## MCP tools (6)

### `list_tasks` (~62 tokens)

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.

Input parameters:

- `day` (string): Defaults to all.
- `status` (string): Defaults to open.

### `add_task` (~169 tokens)

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.

Input parameters:

- `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, required): What to do, e.g. "call Sam 2pm".

### `complete_task` (~34 tokens)

Mark a task done, or reopen it.

Input parameters:

- `done` (boolean): Defaults to true.
- `id` (string, required)

### `update_task` (~59 tokens)

Change a task's title, due time or day. Pass dueAt as null to clear the time.

Input parameters:

- `day` (string)
- `dueAt` (string|null)
- `id` (string, required)
- `title` (string)

### `delete_task` (~20 tokens)

Delete a task permanently.

Input parameters:

- `id` (string, required)

### `get_report` (~49 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/gaby3637-petodo/petodo-cli#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 65
- 2026-11-12: 65
- 2026-11-11: 50

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/petodo-cli
- Socket report: https://socket.dev/npm/package/petodo-cli
- Repository: https://github.com/gaby3637/petodo-cli
- Website: https://petodoapp.com/
- Changelog RSS feed: https://verifymcp.io/servers/gaby3637-petodo/petodo-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/gaby3637-petodo/petodo-cli/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/gaby3637-petodo/petodo-cli.json
- HTML version of this page: https://verifymcp.io/servers/gaby3637-petodo/petodo-cli
