Mindwtr
NPM · MINDWTR-MCP · SCANNED SEP 21
Task and project automation for local and self-hosted Mindwtr Cloud data; read-only by default.
Available components
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 Security96
- 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
- 24 of 38 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dongdongbh/Mindwtr). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2478 tokens (~91/item across 27 items; 27 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 37% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "mindwtr_delete_task" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 27 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
How do I install the Mindwtr MCP server?
Mindwtr runs locally as an npm package, launched with npx -y mindwtr-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mindwtr-mcp
claude mcp add dongdongbh-mindwtr -- npx -y mindwtr-mcp
{
"mcpServers": {
"dongdongbh-mindwtr": {
"command": "npx",
"args": [
"-y",
"mindwtr-mcp"
]
}
}
} {
"servers": {
"dongdongbh-mindwtr": {
"command": "npx",
"args": [
"-y",
"mindwtr-mcp"
]
}
}
} codex mcp add dongdongbh-mindwtr -- npx -y mindwtr-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dongdongbh-mindwtr": {
"type": "local",
"command": [
"npx",
"-y",
"mindwtr-mcp"
],
"enabled": true
}
}
} openclaw mcp add dongdongbh-mindwtr --command npx --arg -y --arg mindwtr-mcp
mcp_servers:
dongdongbh-mindwtr:
command: "npx"
args: ["-y", "mindwtr-mcp"] {
"McpServers": {
"dongdongbh-mindwtr": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mindwtr-mcp"
]
}
}
} assistant mcp add dongdongbh-mindwtr -t stdio -c npx -a -y mindwtr-mcp
{
"mcpServers": {
"dongdongbh-mindwtr": {
"command": "npx",
"args": [
"-y",
"mindwtr-mcp"
]
}
}
} 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.
- 21 Sept 26 −3
- Stability: pass → 0.80 functional
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Stability: 0.87 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.1.8 → 1.1.9 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −3
- Stability: pass → 0.80 functional
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → pass ▲ functional
- 12 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
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 21 Sept 2026 · Analysed npm/mindwtr-mcp@1.1.9
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 | dongdongbh/Mindwtr |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dongdongbh/Mindwtr/.github/workflows/publish-mcp.yml@refs/tags/v1.3.1 |
| Rekor log index | 2880084075 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dca6f23d2b37d94ec828145c4d6c92bc97c6a4654927279886b555ef6532150c54c5ce433bbfab7d212fd335efb66d3773dc94940efeb49d2f8a00af8 |
Background: How many MCP packages publish verified provenance →
Dependencies 38 packages
| Packages resolved | 38 |
|---|---|
| Deprecated | 1 |
| Stale | 23 |
| 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 →
mindwtr_add_area ~43
Add an area to the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | – |
| icon | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_add_person ~47
Add a managed person to the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| note | string|null | – | – |
| referenceLink | string|null | – | – |
No output schema declared.
No examples provided.
mindwtr_add_project ~150
Add a project to the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| areaId | string|null | – | – |
| attachments | array | – | Link attachments (kind "link" only): clickable references such as an obsidian:// note, a file:// path or an https:// URL. |
| cancelledAt | – | – | Cancellation time; closes the project and its unfinished tasks while preserving completed work |
| color | string | – | – |
| dueDate | – | – | – |
| isFocused | boolean | – | – |
| isSequential | boolean | – | – |
| reviewAt | – | – | – |
| startDate | – | – | – |
| status | string | – | – |
| supportNotes | string|null | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_add_section ~63
Add a project-scoped section to the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | – | – |
| isCollapsed | boolean | – | – |
| order | integer | – | – |
| projectId | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_add_task ~566
Add a task to the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| areaId | string | – | Area ID (only used when the task has no projectId) |
| assignedTo | string | – | Person this task is assigned to or waiting for |
| attachments | array | – | Link attachments (kind "link" only): clickable references such as an obsidian:// note, a file:// path or an https:// URL. |
| cancelledAt | string | – | Cancellation time in ISO format; archives the task without completion or another recurrence |
| checklist | array | – | Checklist/subtask items |
| contexts | array | – | Context tags (e.g. ["@home", "@work"]) |
| description | string | – | Task description/notes |
| dueDate | string | – | Due date in ISO format |
| energyLevel | string | – | Energy level: low, medium, high |
| isFocusedToday | boolean | – | Marked as today's focus list |
| location | string | – | Free-text location |
| priority | string | – | Priority level: low, medium, high, urgent |
| projectId | string | – | Project ID to assign the task to |
| pushCount | integer | – | How many times dueDate has been pushed later |
| quickAdd | string | – | Quick-add string with natural language parsing (e.g. "Buy milk @errands #shopping /due:tomorrow +ProjectName") |
| recurrence | – | – | Recurrence object or RFC 5545 RRULE string |
| relativeStartOffset | object | – | Offset from dueDate that recomputes startTime when dueDate changes |
| repeatReminderMinutes | integer | – | Repeat the due-time reminder every N minutes (presets 5|10|15|30|60); 0/absent = off |
| reviewAt | string | – | Tickler/review date in ISO format |
| sectionId | string | – | Project section ID to assign the task to |
| showFutureRecurrence | boolean | – | Calendar-only preview of the next recurrence |
| startTime | – | – | Start time in ISO format |
| status | string | – | Task status: inbox, next, waiting, someday, reference, done, archived |
| suppressMindwtrReminders | boolean | – | Skip Mindwtr start/due reminders for this task |
| tags | array | – | Tags (e.g. ["#urgent", "#personal"]) |
| taskMode | string | – | Task mode: task or list (checklist-first) |
| textDirection | string | – | Text direction for title/description |
| timeEstimate | – | – | Time estimate preset or custom:<positive minutes> |
| timeSpentMinutes | integer | – | Total minutes worked on the task |
| title | string | – | Task title |
No output schema declared.
No examples provided.
mindwtr_complete_task ~31
Mark a task as done in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_delete_area ~30
Soft-delete an area in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_delete_person ~31
Soft-delete a managed person in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_delete_project ~30
Soft-delete a project in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_delete_section ~45
Soft-delete a project section in the configured Mindwtr backend. Tasks in the section are kept and moved to no section by core.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_delete_task ~30
Soft-delete a task in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_get_person ~41
Get a single managed person by ID from the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| includeDeleted | boolean | – | – |
No output schema declared.
No examples provided.
mindwtr_get_project ~40
Get a single project by ID from the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| includeDeleted | boolean | – | – |
No output schema declared.
No examples provided.
mindwtr_get_section ~41
Get a single project section by ID from the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| includeDeleted | boolean | – | – |
No output schema declared.
No examples provided.
mindwtr_get_task ~40
Get a single task by ID from the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| includeDeleted | boolean | – | – |
No output schema declared.
No examples provided.
mindwtr_list_areas ~22
List areas from the configured Mindwtr backend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mindwtr_list_people ~30
List managed people from the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDeleted | boolean | – | – |
No output schema declared.
No examples provided.
mindwtr_list_projects ~21
List projects from the configured Mindwtr backend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mindwtr_list_sections ~45
List project sections from the configured Mindwtr backend. Optionally filter by projectId.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDeleted | boolean | – | – |
| projectId | string | – | – |
No output schema declared.
No examples provided.
mindwtr_list_tasks ~273
List tasks from the configured Mindwtr backend. Filter by status, project, date range, today's focus (isFocusedToday), and GTD availability (view). `search` accepts the documented operator language (status:, context:, tag:, project:, due:<=7d, "quoted phrases", -negation) as well as plain text; note that a search always excludes deleted tasks, so includeDeleted has no effect when search is set. Supports sorting by various fields.
| Name | Type | Req | Description |
|---|---|---|---|
| dueDateFrom | string | – | – |
| dueDateTo | – | – | – |
| includeDeleted | boolean | – | – |
| isFocusedToday | boolean | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| projectId | string | – | – |
| search | string | – | – |
| sortBy | string | – | – |
| sortOrder | string | – | – |
| status | string | – | – |
| view | string | – | GTD availability: 'available' = actionable right now (a next action, or a task whose review date has come due, in an active project, past any start date, and not waiting behind an earlier step of a s… |
No output schema declared.
No examples provided.
mindwtr_rename_person ~51
Rename a managed person. By default, matching task assignees are updated too.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| name | string | yes | – |
| updateTasks | boolean | – | – |
No output schema declared.
No examples provided.
mindwtr_restore_task ~32
Restore a soft-deleted task in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
mindwtr_update_area ~52
Update an area in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string|null | – | – |
| icon | string|null | – | – |
| id | string | yes | – |
| name | string | – | – |
No output schema declared.
No examples provided.
mindwtr_update_person ~54
Update managed person metadata in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| name | string | – | – |
| note | string|null | – | – |
| referenceLink | string|null | – | – |
No output schema declared.
No examples provided.
mindwtr_update_project ~159
Update a project in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| areaId | string|null | – | – |
| attachments | – | – | The complete list of link attachments the item should have. Links not listed are removed; file attachments are never touched. Pass null or [] to remove every link. |
| cancelledAt | – | – | Cancellation time; closes the project and its unfinished tasks while preserving completed work |
| color | string|null | – | – |
| dueDate | – | – | – |
| id | string | yes | – |
| isFocused | boolean | – | – |
| isSequential | boolean | – | – |
| reviewAt | – | – | – |
| startDate | – | – | – |
| status | string | – | – |
| supportNotes | string|null | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
mindwtr_update_section ~60
Update a project section in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | – | – |
| id | string | yes | – |
| isCollapsed | boolean | – | – |
| order | integer | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
mindwtr_update_task ~451
Update a task in the configured Mindwtr backend.
| Name | Type | Req | Description |
|---|---|---|---|
| areaId | string|null | – | Area ID (only used when the task has no projectId) |
| assignedTo | string|null | – | – |
| attachments | – | – | The complete list of link attachments the item should have. Links not listed are removed; file attachments are never touched. Pass null or [] to remove every link. |
| boardOrder | – | – | Manual ordering within a Board status column |
| cancelledAt | – | – | Cancellation time in ISO format; archives the task without completion or another recurrence |
| checklist | – | – | Checklist/subtask items |
| contexts | – | – | – |
| description | string|null | – | – |
| dueDate | – | – | – |
| energyLevel | – | – | – |
| focusOrder | – | – | Manual ordering within Today's Focus |
| id | string | yes | – |
| isFocusedToday | boolean | – | Marked as today's focus list |
| location | string|null | – | Free-text location |
| order | – | – | Manual ordering within a sequential project |
| priority | – | – | – |
| projectId | string|null | – | – |
| pushCount | – | – | How many times dueDate has been pushed later |
| recurrence | – | – | Recurrence object or RFC 5545 RRULE string; null clears it |
| relativeStartOffset | – | – | Offset from dueDate that recomputes startTime when dueDate changes |
| repeatReminderMinutes | – | – | Repeat the due-time reminder every N minutes (presets 5|10|15|30|60); 0/absent = off |
| reviewAt | – | – | Tickler/review date in ISO format |
| sectionId | string|null | – | – |
| showFutureRecurrence | boolean | – | Calendar-only preview of the next recurrence |
| startTime | – | – | – |
| status | string | – | – |
| suppressMindwtrReminders | boolean | – | Skip Mindwtr start/due reminders for this task |
| tags | – | – | – |
| taskMode | – | – | Task mode: task or list (checklist-first) |
| textDirection | – | – | Text direction for title/description |
| timeEstimate | – | – | – |
| timeSpentMinutes | – | – | Total minutes worked on the task |
| title | string | – | – |
No output schema declared.
No examples provided.
What is the Mindwtr MCP server?
Mindwtr is an MCP server listed in the public MCP registry as io.github.dongdongbh/mindwtr. Task and project automation for local and self-hosted Mindwtr Cloud data; read-only by default. This page covers its npm package (mindwtr-mcp).
Is the Mindwtr MCP server safe to use?
Mindwtr scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 Mindwtr MCP server expose?
Mindwtr exposes 27 tools: mindwtr_list_tasks, mindwtr_list_projects, mindwtr_get_project, mindwtr_list_sections, mindwtr_get_section, and 22 more. Their descriptions and schemas cost roughly 2,478 tokens of context every time the server is loaded.
Is the Mindwtr MCP server still maintained?
Mindwtr is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Mindwtr MCP server under?
Mindwtr declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.