Skills/PyPI/todoist-mcp-helper

todoist-mcp-helper@1.2.0

VERIFIED· not started

Publisher claims: "MCP Server for Todoist — Connect AI agents to your Todoist tasks" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher littlepeter52012 · publishing for 271 daysInstalls 54Last detonated 1 h ago
$claude mcp add todoist-mcp-helper -- uvx todoist-mcp-helper
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
TODOIST_API_TOKENConfiguration, not credentials: EXEC_PATH
Where it talks to
no vendor host named in the codeAlso todoist.com — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names todoist.com as well as its own vendor. The guard injects TODOIST_API_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx todoist-mcp-helper

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 3 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.1sprocessexec /usr/bin/dirname
0.1sprocessexited 1:
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.3sprocesssecond launch, clock +45 days, CI unset
0.3sprocessexec /usr/bin/dirname
0.3sprocessexec venv/bin/pip
0.3sprocessexited 127: ./install.sh: line 21: venv/bin/pip: No such file or directory

Static findings

LOW
HTML comment carrying imperative instructions to the agentdonate.html:352 · HTML comment carrying imperative instructions to the agent · informational: not an instruction fileToken selectorFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01

No other findings across 2,600 lines in 14 files.

Cost to the agent

Instructions loaded
≈55 tok
1 file · 14 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for todoist-mcp-helper@1.2.0 as of 28 min ago. This is the package itself, not its dependencies.