0.43.0 → 0.43.1
patch release, 31 March 2026No tool definition changed.
MCP servers / task-master-ai
task-master-ai
1 of its last 5 updates changed what the agent reads: 0 tool descriptions rewritten, up to 0.43.1.
npm package · npm page · recorded on 24 October 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. Method and limits.
Release by release
0.42.0 → 0.43.0
minor release, 4 February 2026update_subtask: input schema changed; new arguments: metadata
0.41.0 → 0.42.0
minor release, 15 January 2026No tool definition changed.
0.40.1 → 0.41.0
minor release, 11 January 2026No tool definition changed.
0.40.0 → 0.40.1
patch release, 28 December 2025No tool definition changed.
Releases tried: 0.40.0 (2025-12-19); 0.40.1 (2025-12-28); 0.41.0 (2026-01-11); 0.42.0 (2026-01-15); 0.43.0 (2026-02-04); 0.43.1 (2026-03-31).
Tools in 0.43.1
The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition.
| Tool | Description | Pin |
|---|---|---|
| get_tasks | Get all tasks from Task Master, optionally filtering by status and including subtasks. | 552b8c99de4b |
| next_task | Find the next task to work on based on dependencies and status | 20f607112bb8 |
| get_task | Get detailed information about a specific task | 9e711079e3f5 |
| set_task_status | Set the status of one or more tasks or subtasks. | f47246e2fb8f |
| update_subtask | Appends timestamped information to a specific subtask without replacing existing content. If you just want to update the subtask status, use set_task_status instead. | 8355747d66cb |
| parse_prd | Parse a Product Requirements Document (PRD) text file to automatically generate initial tasks. Reinitializing the project is not necessary to run this tool. It is recommended to run parse-prd after initializing the project and creating/importing a prd.txt file in the project root's .taskmaster/docs directory. | bfc025d146c4 |
| expand_task | Expand a task into subtasks for detailed implementation | f54fd86746b8 |
Lock these tools
Pin what task-master-ai serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.
$ pip install verfy
$ verfy lock check --update # shows each tool, then writes verfy.lock
$ git add verfy.lock# .github/workflows/verfy.yml, after actions/checkout
- uses: anvarbekovjavohir277-dot/verfy-action@v1Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.