Taskchampion MCP Server
taskchampion-mcp
PyPI
v1.0.4
Published by gabiup2 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Model Context Protocol server for Taskwarrior 3.x, TaskChampion, and Timewarrior
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (src/taskchampion_mcp/cli.py)MTC-SRC-002
In the server's implementation (`src/taskchampion_mcp/cli.py:65`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: th argument list (never shell=True). This is the ONLY place subprocess is invoked in the entire codebase. """
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/taskchampion_mcp/cli.py
Tools 35
Each tool and what it can reach — statically extracted from the published source.
reload_configurationreads sensitive dataanalyze_existing_tasks_for_schemano sensitive capabilityanalyze_taxonomy_fileno sensitive capabilityannotate_taskno sensitive capabilitybatch_create_tasksno sensitive capabilitybulk_modifyno sensitive capabilitycomplete_taskno sensitive capabilitycreate_subtaskno sensitive capabilitycreate_taskno sensitive capabilitydelete_taskno sensitive capability
Show 25 more tools ↓
generate_initial_schema_previewno sensitive capabilityget_active_contextno sensitive capabilityget_initialization_statusno sensitive capabilityget_projectsno sensitive capabilityget_runtime_capabilitiesno sensitive capabilityget_schema_infono sensitive capabilityget_tagsno sensitive capabilityget_taskno sensitive capabilityget_task_reportno sensitive capabilityget_time_statusno sensitive capabilityget_time_summaryno sensitive capabilitylist_preset_schemasno sensitive capabilitylist_tasksno sensitive capabilitymodify_taskno sensitive capabilitypropose_initialization_optionsno sensitive capabilitysave_initial_schemano sensitive capabilitysearch_tasksno sensitive capabilityset_active_schemano sensitive capabilityset_roleno sensitive capabilityset_taxonomy_pathno sensitive capabilitystart_taskno sensitive capabilitystop_taskno sensitive capabilitysync_tasksno sensitive capabilityundo_last_actionno sensitive capabilityuse_preset_schemano sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (35 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.4 latest |
A 93/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan taskchampion-mcp --online --registry pypiMore in Productivity & Workflow
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互：发送消息、图片，等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.