Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.yaminbkk/nexusmem

NPM · NEXUSMEM · SCANNED AUG 17

Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.

Available components

70 Trust /100
Trust breakdown (6 categories)

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 →

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
  • 51 of 138 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability84
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 501 tokens (~125/item across 4 items; 4 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · nexusmem

# add to Claude Code
claude mcp add yaminbkk-nexusmem -- npx -y nexusmem
# add to Codex CLI
codex mcp add yaminbkk-nexusmem -- npx -y nexusmem
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yaminbkk-nexusmem": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "nexusmem"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add yaminbkk-nexusmem --command npx --arg -y --arg nexusmem
# ~/.hermes/config.yaml
mcp_servers:
  yaminbkk-nexusmem:
    command: "npx"
    args: ["-y", "nexusmem"]
// mcp.json
{
  "mcpServers": {
    "yaminbkk-nexusmem": {
      "command": "npx",
      "args": [
        "-y",
        "nexusmem"
      ]
    }
  }
}
Changelog

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 Aug 26 70

    First indexed and scored.

Diagnostics

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 17 Aug 2026 · Analysed npm/nexusmem@0.3.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 138 packages
Packages resolved 138
Deprecated 1
Stale 50
Tree resolution Complete
MCP tools · 4 exposed · ~501 tokens

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.

Tool Tokens
get_status ~41

Report how many nodes NexusMem currently remembers for a repository, broken down by kind and source.

NameTypeReqDescription
projectRootstringyesAbsolute path to the repository root

No output schema declared.

No examples provided.

list_recent_memory ~98

List the most recently remembered items for a NexusMem-tracked repository -- git commits, code diffs, shell commands, tracked docs, and (if enabled) conversation transcripts and session summaries -- newest first. Chronological, not relevance-ranked: use search_memory instead for a specific question.

NameTypeReqDescription
limitintegerMax items to return, newest first. Default 20.
projectRootstringyesAbsolute path to the repository root

No output schema declared.

No examples provided.

search_memory ~171

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 and per-session summaries. Returns a token-budgeted, ranked context block -- not raw search results.

NameTypeReqDescription
allProjectsbooleanSearch 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…
budgetintegerMax tokens in the returned context block. Default 2000.
projectRootstringyesAbsolute path to the repository root
querystringyesFree-text question or search terms

No output schema declared.

No examples provided.

sync_project ~191

Ingest new git, diff, shell, docs and (if enabled) conversation 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.

NameTypeReqDescription
projectRootstringyesAbsolute path to the repository root
pruneSourcestringDelete every node from this exact source (e.g. "shell:pwsh") instead of syncing
pruneStaleShellbooleanShortcut for pruneSource on shell:pwsh, shell:bash and shell:zsh at once -- the dead pre-hook scrape sources
yesbooleanConfirms the delete. Without it, pruneSource/pruneStaleShell only report the matching count.

No output schema declared.

No examples provided.