TaskManagerSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Model Context Protocol server for Task Management. This allows Claude Desktop (or any MCP client) to manage and execute tasks in a queue-based system.
Quick Start (For Users)
Prerequisites
- Node.js 18+ (install via
brew install node) - Claude Desktop (install from https://claude.ai/desktop)
Configuration
- Open your Claude Desktop configuration file at:
~/Library/Application Support/Claude/claude_desktop_config.json
You can find this through the Claude Desktop menu:
- Open Claude Desktop
- Click Claude on the Mac menu bar
- Click "Settings"
- Click "Developer"
- Add the following to your configuration:
{
"tools": {
"taskmanager": {
"command": "npx",
"args": ["-y", "@kazuph/mcp-taskmanager"]
}
}
}For Developers
Prerequisites
- Node.js 18+ (install via
brew install node) - Claude Desktop (install from https://claude.ai/desktop)
- tsx (install via
npm install -g tsx)
Installation
git clone https://github.com/kazuph/mcp-taskmanager.git cd mcp-taskmanager npm install npm run build
Development Configuration
- Make sure Claude Desktop is installed and running.
- Install tsx globally if you haven't:
npm install -g tsx # or pnpm add -g tsx
- Modify your Claude Desktop config located at:
~/Library/Application Support/Claude/claude_desktop_config.json
Add the following to your MCP client's configuration:
{
"tools": {
"taskmanager": {
"args": ["tsx", "/path/to/mcp-taskmanager/index.ts"]
}
}
}Available Operations
The TaskManager supports two main phases of operation:
Planning Phase
- Accepts a task list (array of strings) from the user
- Stores tasks internally as a queue
- Returns an execution plan (task overview, task
30b6ee563032OBSERVED · 2026-10-06Connect
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 mcp add mcp-taskmanager -- npx -y @kazuph/[email protected]
{
"mcpServers": {
"mcp-taskmanager": {
"command": "npx",
"args": [
"-y",
"@kazuph/[email protected]"
]
}
}
}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.
| Tool | Risk | Description |
|---|---|---|
add_tasks_to_request | write | Add new tasks to an existing request. This allows extending a request with additional tasks.\n\n |
approve_request_completion | read | After all tasks are done and approved, this tool finalizes the entire request. The user must call this to confirm that the request is fully completed.\n\n |
approve_task_completion | read | Once the assistant has marked a task as done using |
delete_task | destructive | Delete a specific task from a request. Only uncompleted tasks can be deleted.\n\n |
get_next_task | read | Given a |
list_requests | read | List all requests with their basic information and summary of tasks. This provides a quick overview of all requests in the system. |
mark_task_done | read | Mark a given task as done after you |
open_task_details | read | Get details of a specific task by |
request_planning | read | Register a new user request and plan its associated tasks. You must provide |
update_task | write | Update an existing task |
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.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
delete_task
@modelcontextprotocol/sdk, zod, @types/node, shx, typescript, vitest
Gates applied: no_behavioural_pass.
30b6ee563032full audit observations/trust-audit/mcp-server/kazuph__taskmanager.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-06 | 30b6ee563032 | SAFE | B | 89 | first audit |
Questions
What tools does TaskManager expose?
10 in total: 7 read-only, 2 that write, and 1 that can delete or overwrite (delete_task). Every one is listed on this page with its risk.
Is TaskManager 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 TaskManager need?
No credential environment variables were found in its source, so it appears to need none.
How does TaskManager run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @kazuph/mcp-taskmanager at 1.1.1.
How current is this page?
The grade is for one exact copy of the source (30b6ee563032), read on 2026-10-06. The repository is watched and re-audited when it changes.