io.github.mahmoud-nb/thread-mind
NPM · THREAD-MIND-MCP
Git-friendly memory for AI coding: a tree of thread summaries with inherited context
Available components
Last scanned (21 hours ago)
Scores higher than 69% of npm servers
Category Memory and Knowledge
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 Security98
- 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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1350 tokens (~84/item across 16 items; 14 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +7
- Stability: unverified → 0.50 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 72
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 16 Oct 2026 · Analysed npm/thread-mind-mcp@0.5.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
context_get Get thread context ~60
Get the assembled context of the active thread: its summary plus the decisions and constraints of its ancestors. Call it once at the start of a session.
| Name | Type | Req | Description |
|---|---|---|---|
| maxTokens | integer | – | Token budget: the farthest ancestors are left out first to fit it |
No output schema declared.
No examples provided.
project_create Create project ~59
Create a new ThreadMind project with a main thread
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Project mode: solo (default) or team |
| systemContext | string | – | System context or instructions for this project |
| title | string | yes | Project title |
No output schema declared.
No examples provided.
project_list List projects ~14
List all ThreadMind projects
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_switch Switch project ~27
Switch to a different project
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Project ID to switch to |
No output schema declared.
No examples provided.
stats_show Show statistics ~26
Show the size of each summary and, with the Claude Code plugin, measured conversation sizes
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
summary_update Update thread summary ~160
Update the summary of a thread (markdown). With a section, adds to that section only (or replaces it with replaceSection); without one, replaces the whole summary, so keep what is still true.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The new summary, or the text to add to the section (markdown) |
| paths | array | – | Files or directories this thread is about, used to flag the summary when they change |
| replaceSection | boolean | – | Replace the section instead of adding to it (use it for state and next-steps) |
| section | string | – | Only update this section: decisions, constraints, state, open-questions or next-steps |
| threadId | string | – | Thread ID to update (defaults to active thread) |
No output schema declared.
No examples provided.
thread_create Create thread ~65
Create a new child thread branching from a parent thread, and make it the active thread. On a feature branch, the thread is linked to that branch.
| Name | Type | Req | Description |
|---|---|---|---|
| parentId | string | – | Parent thread ID (defaults to current active thread) |
| title | string | yes | Thread title |
No output schema declared.
No examples provided.
thread_delete Delete thread ~28
Delete a thread and all its descendants
| Name | Type | Req | Description |
|---|---|---|---|
| threadId | string | yes | Thread ID to delete |
No output schema declared.
No examples provided.
thread_list Show thread tree ~26
Display the thread tree for the active project, with each thread's status and linked branch
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
thread_merge Merge thread into parent ~83
Fold a finished thread into its parent: replaces the parent's summary with parentSummary, marks the thread done and switches to the parent. Write parentSummary yourself, including the thread's conclusions.
| Name | Type | Req | Description |
|---|---|---|---|
| parentSummary | string | yes | The parent's new summary, including the merged thread's conclusions (markdown) |
| threadId | string | – | Thread ID to merge (defaults to active thread) |
No output schema declared.
No examples provided.
thread_rebase Move thread ~58
Move a thread to a different parent. All descendants move with it. Similar to git rebase.
| Name | Type | Req | Description |
|---|---|---|---|
| newParentId | string | yes | ID of the new parent thread |
| threadId | string | yes | ID of the thread to move |
No output schema declared.
No examples provided.
thread_status Set thread status ~75
Mark a thread as done or abandoned (or active again). The reason is added to the thread's decisions, so the outcome stays on record.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Why the thread is done or abandoned |
| status | string | yes | New status |
| threadId | string | – | Thread ID (defaults to active thread) |
No output schema declared.
No examples provided.
thread_switch Switch thread ~64
Switch this session to a different thread and return its assembled context (no need to call context_get afterwards)
| Name | Type | Req | Description |
|---|---|---|---|
| maxTokens | integer | – | Token budget: the farthest ancestors are left out first to fit it |
| threadId | string | yes | Thread ID to switch to |
No output schema declared.
No examples provided.
threadmind_init Generate instruction files ~109
Write ThreadMind usage instructions into the files AI agents read. Claude Code doesn't need them: it receives these instructions from this server.
| Name | Type | Req | Description |
|---|---|---|---|
| clients | array | – | Files to generate: "agents" (AGENTS.md, read by Codex, Cursor, Copilot and others), "claude" (CLAUDE.md), "cursor" (.cursor/rules/threadmind.mdc), "generic" (.threadmind/instructions.md, to paste int… |
No output schema declared.
No examples provided.
How do I install the io.github.mahmoud-nb/thread-mind MCP server?
io.github.mahmoud-nb/thread-mind runs locally as an npm package, launched with npx -y thread-mind-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 · thread-mind-mcp
claude mcp add mahmoud-nb-thread-mind -- npx -y thread-mind-mcp
What is the io.github.mahmoud-nb/thread-mind MCP server?
io.github.mahmoud-nb/thread-mind is an MCP server listed in the public MCP registry as io.github.mahmoud-nb/thread-mind. Git-friendly memory for AI coding: a tree of thread summaries with inherited context. This page covers its npm package (thread-mind-mcp).
Is the io.github.mahmoud-nb/thread-mind MCP server safe to use?
io.github.mahmoud-nb/thread-mind scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. 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 io.github.mahmoud-nb/thread-mind MCP server expose?
io.github.mahmoud-nb/thread-mind exposes 14 tools: project_create, project_list, project_switch, thread_create, thread_switch, and 9 more. Their descriptions and schemas cost roughly 854 tokens of context every time the server is loaded.
Is the io.github.mahmoud-nb/thread-mind MCP server still maintained?
io.github.mahmoud-nb/thread-mind is still listed as active in the MCP registry. We last reached this channel on 16 October 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 io.github.mahmoud-nb/thread-mind MCP server under?
io.github.mahmoud-nb/thread-mind declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.