Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/AlonTsur1601/TodoMCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/alontsur1601/todomcp/todo-mcp)<a href="https://agentmods.dev/mcp/alontsur1601/todomcp/todo-mcp"><img src="https://agentmods.dev/badge/mcp/alontsur1601/todomcp/todo-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/alontsur1601/todomcp/todo-mcp"><img src="https://agentmods.dev/badge/mcp/alontsur1601/todomcp/todo-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
todo-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "todo-mcp": { "command": "npx", "args": [ "-y", "todo-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 9 lines scan A a61ca76165a9
todo-mcp is an MCP server published in the GitHub repository AlonTsur1601/TodoMCP (1 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
atomlane
MCP server "atomlane" as configured in cloudguo123/atomlane. Runs ./scripts/mcp_server.py with python3.
proton-drive-cli
Manage Proton Drive from Claude, Codex, VS Code/Copilot, and other MCP clients through Proton's official CLI without exposing Proton credentials. Runs locally from the @borealstack/proton-drive-cli-mcp npm package.
mcp-google-tasks
MCP server for the Google Tasks API — manage task lists, create and organize tasks with due dates, notes and subtasks, track completion and sync changes. For Claude, Cursor, Codex and other AI clients. Runs locally from the mcp-google-tasks npm package.
habitica
MCP server "habitica" as configured in rodcordeiro/habitica-mcp. Runs ../../dist/index.js with node. Needs 3 environment variables to run.
woven
MCP server "woven" as configured in Ducksss/LifeHack-2026. Runs ./node_modules/tsx/dist/cli.mjs with node. Needs 2 environment variables to run.
calendly-mcp
MCP server connecting Claude Desktop/Code to Calendly for natural-language scheduling management. Runs locally from the calendly-mcp Python package.