projectmind
NPM · @NODEMINT/PROJECTMIND · SCANNED SEP 30
Persistent project memory for AI coding agents: one compact digest instead of re-reading the repo.
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 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 85 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 740 tokens (~105/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 projectmind MCP server?
projectmind runs locally as an npm package, launched with npx -y @nodemint/projectmind. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @nodemint/projectmind
claude mcp add nodemint-dev-projectmind -- npx -y @nodemint/projectmind
{
"mcpServers": {
"nodemint-dev-projectmind": {
"command": "npx",
"args": [
"-y",
"@nodemint/projectmind"
]
}
}
} {
"servers": {
"nodemint-dev-projectmind": {
"command": "npx",
"args": [
"-y",
"@nodemint/projectmind"
]
}
}
} codex mcp add nodemint-dev-projectmind -- npx -y @nodemint/projectmind
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nodemint-dev-projectmind": {
"type": "local",
"command": [
"npx",
"-y",
"@nodemint/projectmind"
],
"enabled": true
}
}
} openclaw mcp add nodemint-dev-projectmind --command npx --arg -y --arg @nodemint/projectmind
mcp_servers:
nodemint-dev-projectmind:
command: "npx"
args: ["-y", "@nodemint/projectmind"] {
"McpServers": {
"nodemint-dev-projectmind": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@nodemint/projectmind"
]
}
}
} assistant mcp add nodemint-dev-projectmind -t stdio -c npx -a -y @nodemint/projectmind
{
"mcpServers": {
"nodemint-dev-projectmind": {
"command": "npx",
"args": [
"-y",
"@nodemint/projectmind"
]
}
}
} 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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- 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 −3
- Stability: pass → 0.80 functional
- 26 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 21 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.
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 30 Sept 2026 · Analysed npm/@nodemint/projectmind@0.6.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 →
mind_context ~148
Call this BEFORE reading/greping files, when you're about to work on specific files or a module and want its purpose, notes, and direct dependencies without opening them. Given the files you're about to edit (and/or a node id or keyword), returns ONLY the relevant part of the map. Use this over mind_digest when you already know which files a task touches — it's the most surgical, token-cheap option.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | number | – | Neighbor expansion depth (default 1). |
| files | array | – | Repo-relative paths you're working on. |
| node | string | – | Seed the subgraph from this node id. |
| term | string | – | Seed the subgraph from a keyword. |
No output schema declared.
No examples provided.
mind_digest ~142
Call this BEFORE running ls, find, glob, grep, tree, or reading any file, whenever the task is to explain, describe, summarize, or give an overview of this project or its architecture, or when you otherwise need to orient yourself in an unfamiliar codebase. This includes questions like "what is this project", "explain this codebase", "what's the tech stack", or "how is this structured" — call mind_digest first, THEN use its output to decide whether further file exploration is even needed. Returns a compact map of modules, dependencies, decisions, and conventions in a few hundred tokens, replacing what would otherwise be many file reads.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mind_handoff ~138
Leave a one-line handoff note — what you were doing and what's next — before the session ends or the context is about to be compacted. It appears at the TOP of the next session's mind_digest, so the next session (yours or a teammate's agent) resumes instantly instead of rediscovering the task. Stored in the developer's local overlay, never committed. Pass clear: true when the noted work is done.
| Name | Type | Req | Description |
|---|---|---|---|
| clear | boolean | – | Clear the current handoff note instead of setting one. |
| note | string | – | One or two lines: what's in progress, what to do next, any gotcha. |
No output schema declared.
No examples provided.
mind_query ~63
Get full detail on ONE node (its files, notes, and edges) when you need to drill into a specific module. Use after mind_digest points you at the right node — cheaper than reading the files.
| Name | Type | Req | Description |
|---|---|---|---|
| node | string | yes | The node id from the digest. |
No output schema declared.
No examples provided.
mind_search ~44
Find nodes, decisions, or glossary terms by keyword. Use to locate the right part of the project without reading files.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | Case-insensitive search term. |
No output schema declared.
No examples provided.
mind_stats ~40
Return map size, the estimated token cost of the digest, and the local savings ledger (estimated tokens/dollars saved by reading the map instead of scanning files).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mind_update ~165
Call this when you add or change a module, make an architectural decision, or learn a project convention — so the next session doesn't have to rediscover it. Do NOT call for trivial edits. Pass ONLY the fields that changed.
| Name | Type | Req | Description |
|---|---|---|---|
| convention | string | – | – |
| decision | object | – | – |
| edge | object | – | – |
| glossary | object | – | term -> definition. |
| local | boolean | – | Write to the per-developer overlay instead of the shared map. |
| node | object | – | Add/update a node. |
| project | object | – | Partial project fields, e.g. { name, description }. |
| removeEdge | object | – | – |
| removeNode | string | – | – |
| stack | array | – | Stack tags to add (set-union). |
No output schema declared.
No examples provided.
What is the projectmind MCP server?
projectmind is an MCP server listed in the public MCP registry as io.github.Nodemint-dev/projectmind. Persistent project memory for AI coding agents: one compact digest instead of re-reading the repo. This page covers its npm package (@nodemint/projectmind).
Is the projectmind MCP server safe to use?
projectmind scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 September 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 projectmind MCP server expose?
projectmind exposes 7 tools: mind_digest, mind_context, mind_query, mind_search, mind_update, and 2 more. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.
Is the projectmind MCP server still maintained?
projectmind is still listed as active in the MCP registry. We last reached this channel on 30 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 projectmind MCP server under?
projectmind declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.