Atlas / MCP servers / regibyte / Todo List

Todo ListSAFE

mcp/regibyte/todo-list

An MCP server for managing todos within LLMs, created for educational purposes

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
10 7r · 2w · 1d
Transport
stdio
License
MIT
Stars
46
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

A Model Context Protocol (MCP) server that provides a comprehensive API for managing todo items.

📚 Learning Resource: This project is designed as an educational example of MCP implementation. See GUIDE.md for a comprehensive explanation of how the project works and why things are implemented the way they are.

Features

  • Create todos: Add new tasks with title and markdown description
  • Update todos: Modify existing tasks
  • Complete todos: Mark tasks as done
  • Delete todos: Remove tasks from the list
  • Search todos: Find tasks by title or creation date
  • Summarize todos: Get a quick overview of active tasks

Tools

This MCP server exposes the following tools:

  1. create-todo: Create a new todo item
  2. list-todos: List all todos
  3. get-todo: Get a specific todo by ID
  4. update-todo: Update a todo's title or description
  5. complete-todo: Mark a todo as completed
  6. delete-todo: Delete a todo
  7. search-todos-by-title: Search todos by title (case-insensitive partial match)
  8. search-todos-by-date: Search todos by creation date (format: YYYY-MM-DD)
  9. list-active-todos: List all non-completed todos
  10. summarize-active-todos: Generate a summary of all active (non-completed) todos

Installation

# Clone the repository
git clone https://github.com/RegiByte/todo-list-mcp.git
cd todo-list-mcp

# Install dependencies
npm install

# Build the project
npm run build

Usage

Starting the Server

npm start

Configuring with Claude for Desktop

Claude Desktop

Add this to your claude_desktop_config.json:

{
"mcpServers": {
"todo": {
"command": "node",
"args": ["/absolute/path/to/todo-list-mcp/dist/index.js"]
}
}
}

Cursor

  • Go to
Read from source at commit 88252a727715OBSERVED · 2026-10-08
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add todo-list-mcp -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "todo-list-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (10)

7 read · 2 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.

ToolRiskDescription
complete-todoreadMark a todo as completed
create-todowriteCreate a new todo item
delete-tododestructiveDelete a todo
get-todoreadGet a specific todo by ID
list-active-todosreadList all non-completed todos
list-todosreadList all todos
search-todos-by-datereadSearch todos by creation date (format: YYYY-MM-DD)
search-todos-by-titlereadSearch todos by title (case insensitive partial match)
summarize-active-todosreadGenerate a summary of all active (non-completed) todos
update-todowriteUpdate a todo title or description
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfaceWARN
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
UNDECLARED (1 observation(s))
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (2)

MEDIUMFilesystem / path · mcp.destructive_tools · CWE-22, CWE-59
delete-todo
Why it matters. 1 tool(s) can delete or overwrite
Fix. prefer a read-only mode or scoped tokens; the page states the blast radius
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, better-sqlite3, typescript, uuid, zod, @modelcontextprotocol/inspector, @types/better-sqlite3, @types/node
Why it matters. 9 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-08 · audit v0.4.1 · source sha 88252a727715full audit observations/trust-audit/mcp-server/regibyte__todo-list.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-0888252a727715SAFEB89first audit
06

Questions

What is the Todo List MCP server?

An MCP server for managing todos within LLMs, created for educational purposes

What tools does Todo List expose?

10 in total: 7 read-only, 2 that write, and 1 that can delete or overwrite (delete-todo). Every one is listed on this page with its risk.

Is Todo List safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.

What credentials does Todo List need?

No credential environment variables were found in its source, so it appears to need none.

How does Todo List run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as todo-list-mcp at 1.0.0.

How current is this page?

The grade is for one exact copy of the source (88252a727715), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement