io.github.yaminbkk/nexusmem
NPM · NEXUSMEM
Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.
Available components
Last scanned (6 hours ago)
Scores higher than 81% 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
- 52 of 135 dependencies flagged as unhealthy (1 deprecated). 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 38 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 831 tokens (~138/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 13 Oct 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.
- 12 Oct 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 11 Oct 26 +1
- Stability: 0.90 → pass security
- Security disclosure: fail → 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 5 Nov 2026 · Analysed npm/nexusmem@0.10.5
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 135 packages
| Packages resolved | 135 |
|---|---|
| Deprecated | 1 |
| Stale | 51 |
| 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 →
get_status Show what is remembered ~41
Report how many nodes NexusMem currently remembers for a repository, broken down by kind and source.
| Name | Type | Req | Description |
|---|---|---|---|
| projectRoot | string | yes | Absolute path to the repository root |
No output schema declared.
No examples provided.
list_recent_memory List recently remembered items ~106
List the most recently remembered items for a NexusMem-tracked repository -- git commits, code diffs, shell commands, tracked docs, and (if enabled) conversation transcripts, session summaries, and github.com issue/PR threads -- newest first. Chronological, not relevance-ranked: use search_memory instead for a specific question.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return, newest first. Default 20. |
| projectRoot | string | yes | Absolute path to the repository root |
No output schema declared.
No examples provided.
list_stale_suggestions List open contradiction suggestions ~107
List open contradiction verdicts for a NexusMem-tracked repository -- candidates flagged by "nexusmem stale --check-contradictions" (or automatically during sync) as likely superseded by a newer, similar node. Nothing has been written yet; use resolve_stale_suggestion to act on one.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max suggestions to return, most recently judged first. Default 50. |
| projectRoot | string | yes | Absolute path to the repository root |
No output schema declared.
No examples provided.
resolve_stale_suggestion Accept or dismiss a contradiction suggestion ~151
"accept" writes a supersede link from candidateId to againstId (the same effect as "nexusmem mark-stale") -- the ranker down-weights candidateId from then on but never deletes it. "dismiss" silences the suggestion without changing ranking, so it stops resurfacing on future stale/sync runs.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Whether to write the supersede link or silence the suggestion |
| againstId | string | – | Id of the superseding node. Required for "accept", ignored for "dismiss". |
| candidateId | string | yes | Id of the stale/superseded node |
| projectRoot | string | yes | Absolute path to the repository root |
No output schema declared.
No examples provided.
search_memory Search remembered project history ~229
Search a NexusMem-tracked repository's remembered history: git commits, code diffs (the patch of each changed file), shell commands, tracked markdown docs, and (if enabled) conversation transcripts, per-session summaries, and github.com issue/PR threads. Returns a token-budgeted, ranked context block -- not raw search results.
| Name | Type | Req | Description |
|---|---|---|---|
| allProjects | boolean | – | Search every repository NexusMem has been run in on this machine, not just projectRoot. Use when the answer may live in a different project (a pattern solved elsewhere, a tool that failed the same wa… |
| asOf | string | – | ISO-8601 date/time. Restricts results to nodes recorded at or before this instant -- "what did memory hold as of then", not "what happened then". Omit for the normal, unrestricted read. |
| budget | integer | – | Max tokens in the returned context block. Default 2000. |
| projectRoot | string | yes | Absolute path to the repository root |
| query | string | yes | Free-text question or search terms |
No output schema declared.
No examples provided.
sync_project Sync remembered history ~197
Ingest new git, diff, shell, docs and (if enabled) conversation and github.com issue/PR history for a NexusMem-tracked repository into its local database. Pass pruneSource or pruneStaleShell instead to delete a dead source's nodes (e.g. the pre-hook shell scrape) rather than syncing -- dry-run unless yes is also true, since this is an irreversible full wipe of that source.
| Name | Type | Req | Description |
|---|---|---|---|
| projectRoot | string | yes | Absolute path to the repository root |
| pruneSource | string | – | Delete every node from this exact source (e.g. "shell:pwsh") instead of syncing |
| pruneStaleShell | boolean | – | Shortcut for pruneSource on shell:pwsh, shell:bash and shell:zsh at once -- the dead pre-hook scrape sources |
| yes | boolean | – | Confirms the delete. Without it, pruneSource/pruneStaleShell only report the matching count. |
No output schema declared.
No examples provided.
How do I install the io.github.yaminbkk/nexusmem MCP server?
io.github.yaminbkk/nexusmem runs locally as an npm package, launched with npx -y nexusmem. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · nexusmem
claude mcp add yaminbkk-nexusmem -- npx -y nexusmem
What is the io.github.yaminbkk/nexusmem MCP server?
io.github.yaminbkk/nexusmem is an MCP server listed in the public MCP registry as io.github.yaminbkk/nexusmem. Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP. This page covers its npm package (nexusmem).
Is the io.github.yaminbkk/nexusmem MCP server safe to use?
io.github.yaminbkk/nexusmem scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.yaminbkk/nexusmem MCP server expose?
io.github.yaminbkk/nexusmem exposes 6 tools: search_memory, sync_project, get_status, list_recent_memory, list_stale_suggestions, resolve_stale_suggestion. Their descriptions and schemas cost roughly 831 tokens of context every time the server is loaded.
Is the io.github.yaminbkk/nexusmem MCP server still maintained?
io.github.yaminbkk/nexusmem is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.yaminbkk/nexusmem MCP server under?
io.github.yaminbkk/nexusmem declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.