Microsoft Todo
NPM · @PIPEWORX/MCP-MICROSOFT-TODO · 2 COMPONENTS
Microsoft To Do (Microsoft 365) MCP Pack
Available components
Last scanned (22 hours ago)
Scores higher than 82% of npm servers
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-microsoft-todo). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 456 tokens (~114/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +2
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 82
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@pipeworx/mcp-microsoft-todo@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-microsoft-todo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-microsoft-todo/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655464487 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:64037cfd19f85c6c1565d1965096b7d86c139d68ff676432d5547e7cf176c4e0d0abce4dc5faf8cab4dcd46431f9116cd7a76bcd1ebd4188b4ca4fe7c |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_due_tasks ~94
Find upcoming, incomplete Microsoft To Do tasks across all of the user's to-do lists that are due within the next N days. Returns a flat list of due reminders with their list name, title, due date, and importance. Use to answer "what tasks are due soon" or "what are my upcoming reminders".
| Name | Type | Req | Description |
|---|---|---|---|
| days_ahead | number | – | How many days ahead to look for due tasks (default 7). |
No output schema declared.
No examples provided.
get_task ~118
Get the full details of a single Microsoft To Do task by its list ID and task ID, including title, status, importance, full body/notes, due date, reminder time, created/completed times, and any checklist (sub-task) items. Use after list_tasks or find_due_tasks to read a to-do item in full.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The ID of the Microsoft To Do task list containing the task. |
| task_id | string | yes | The ID of the task to retrieve (from a list or find result). |
No output schema declared.
No examples provided.
list_task_lists ~63
List the Microsoft To Do task lists for the signed-in user, with display names and whether each is a well-known list (e.g. the default "Tasks" or flagged-email list). Use to discover a to-do list and its ID before listing tasks or reminders.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tasks ~126
List the tasks in a Microsoft To Do list. Returns compact task summaries (title, status, importance, due date, created/completed times, and a body preview). Optionally filter by status. Use to browse a user's to-do list and see what tasks or reminders it contains.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The ID of the Microsoft To Do task list to read (from list_task_lists). |
| status | string | – | Optional filter restricting results to tasks with this status. |
| top | number | – | Maximum number of tasks to return (default 50, max 100). |
No output schema declared.
No examples provided.
How do I install the Microsoft Todo MCP server?
Microsoft Todo runs locally as an npm package, launched with npx -y @pipeworx/mcp-microsoft-todo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-microsoft-todo
claude mcp add pipeworx-io-microsoft-todo -- npx -y @pipeworx/mcp-microsoft-todo
What is the Microsoft Todo MCP server?
Microsoft Todo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/microsoft-todo. Microsoft To Do (Microsoft 365) MCP Pack. This page covers its npm package (@pipeworx/mcp-microsoft-todo).
Is the Microsoft Todo MCP server safe to use?
Microsoft Todo scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Microsoft Todo MCP server expose?
Microsoft Todo exposes 4 tools: list_task_lists, list_tasks, get_task, find_due_tasks. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.
Is the Microsoft Todo MCP server still maintained?
Microsoft Todo is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Microsoft Todo MCP server under?
Microsoft Todo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.