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.donggyun112/keymem

NPM · KEYMEM · SCANNED SEP 21

Associative key-graph memory for LLM agents — recall by association, not vector similarity.

Available components

0 this week 76 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects tar 6.2.1, reached via fastembed > tar. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 65 of 177 dependencies flagged as unhealthy (4 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1349 tokens (~122/item across 11 items; 11 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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cleanup_expired" 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 12 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
Install

How do I install the io.github.donggyun112/keymem MCP server?

io.github.donggyun112/keymem runs locally as an npm package, launched with npx -y keymem. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · keymem

# add to Claude Code
claude mcp add donggyun112-keymem -- npx -y keymem
// .cursor/mcp.json
{
  "mcpServers": {
    "donggyun112-keymem": {
      "command": "npx",
      "args": [
        "-y",
        "keymem"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "donggyun112-keymem": {
      "command": "npx",
      "args": [
        "-y",
        "keymem"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add donggyun112-keymem -- npx -y keymem
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "donggyun112-keymem": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "keymem"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add donggyun112-keymem --command npx --arg -y --arg keymem
# ~/.hermes/config.yaml
mcp_servers:
  donggyun112-keymem:
    command: "npx"
    args: ["-y", "keymem"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "donggyun112-keymem": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "keymem"
      ]
    }
  }
}
# add to Vellum
assistant mcp add donggyun112-keymem -t stdio -c npx -a -y keymem
// mcp.json
{
  "mcpServers": {
    "donggyun112-keymem": {
      "command": "npx",
      "args": [
        "-y",
        "keymem"
      ]
    }
  }
}
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.

  • 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.

  • 19 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 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 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.

  • 13 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
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 21 Sept 2026 · Analysed npm/keymem@0.17.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 →

Vulnerabilities 12 findings
ID CVE Severity Vector Fix available
GHSA-23hp-3jrh-7fpw CVE-2026-59873 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-34x7-hfp2-rc4v CVE-2026-24842 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N yes
GHSA-83g3-92jg-28cx CVE-2026-26960 high CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N yes
GHSA-8qq5-rm4j-mr97 CVE-2026-23745 high yes
GHSA-8x88-c5mf-7j5w CVE-2026-59874 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9ppj-qmqm-q256 CVE-2026-31802 high yes
GHSA-gvwx-54wh-qm9j CVE-2026-59875 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-qffp-2rhf-9h96 CVE-2026-29786 high yes
GHSA-r292-9mhp-454m CVE-2026-73566 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-r6q2-hw4h-h46w CVE-2026-23950 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L yes
GHSA-vmf3-w455-68vh CVE-2026-53655 medium yes
GHSA-w8wr-v893-vjvp CVE-2026-59871 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 177 packages
Packages resolved 177
Deprecated 4
Stale 60
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,055 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. 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 →

Tool Tokens
cleanup_expired ~29

Delete all memories past their ttl. Returns count of deleted memories. Call periodically to keep memory clean.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

correct ~106

Update outdated information. Use when user corrects you or info changes (e.g. moved cities, changed job). Old version is preserved but weakened — never lost. Omit keys to keep the same search terms. related_to links the updated memory to other memory IDs.

NameTypeReqDescription
contentstringyes
key_typesobject
keysarray
memory_idstringyes
related_toarray
sourceobject

No output schema declared.

No examples provided.

forget ~41

Permanently delete a memory. Only use for completely wrong information. For outdated info, use correct() instead — it preserves history.

NameTypeReqDescription
memory_idstringyes

No output schema declared.

No examples provided.

list_memories ~40

List all stored memories. namespace filters by project/context. Expired memories are excluded. Prefer recall() for normal retrieval.

NameTypeReqDescription
namespacestring

No output schema declared.

No examples provided.

memory_stats ~21

Get counts of keys, memories, and links in the system.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_key ~130

List the memories stored under one key (concept), ranked. Returns the canonical key, its aliases, and hub metadata plus ranked memory IDs and metadata — never memory content. Call read_memory on promising handles. Use limit/offset to page through hub keys without flooding context. Pass the original query: handles are then ranked by content relevance to it, which is essential for hub keys so the target memory surfaces first instead of being buried.

NameTypeReqDescription
key_idstringyes
limitnumber
namespacestring
offsetnumber
querystring

No output schema declared.

No examples provided.

read_memory ~97

Read the full content of one stored memory (selected via read_key). Returns the memory and all connected key clusters so exploration can continue Key → Memory → Key. Pass via_key_id from the selected key: only that traversed edge is Hebbian-reinforced, and depth/access count increase only when this full read occurs.

NameTypeReqDescription
memory_idstringyes
namespacestring
via_key_idstring

No output schema declared.

No examples provided.

recall ~263

Search long-term memory for what is already known about the user, project, or topic — call this before your first reply and whenever the topic shifts. Returns matching key clusters only (not memory content): canonical concept, aliases, key type, match score, linked-memory count, hub status, and specificity. Follow up with read_key(key_id) then read_memory(memory_id, via_key_id) to read a stored fact. Use short focused noun queries and decompose multi-fact questions into several recall calls. Set inject:true to ALSO get the top connected memories' content in one call (skips manual read_key/read_memory) — returns {keys, memories}. Opt-in: trades the deliberate-navigation flow's context-efficiency and precision (the injected set carries lower-precision associative neighbours) for fewer round trips. inject_top_k caps the injected set; inject_prefer_depth favors confirmed (deep) memories; inject_explore_shallow reserves one slot for a weak/recent memory.

NameTypeReqDescription
injectboolean
inject_explore_shallowboolean
inject_prefer_depthboolean
inject_top_knumber
namespacestring
querystringyes
top_knumber

No output schema declared.

No examples provided.

related ~59

Find other memories associated with a memory you already have (by ID). Returns neighboring memories connected by shared keys or explicit links. For normal agent-driven navigation prefer read_memory(), inspect its returned keys, then call read_key().

NameTypeReqDescription
memory_idstringyes

No output schema declared.

No examples provided.

remember ~213

Save important information to memory. Keys are search terms — think 'what would I search to find this later?' Use 3-6 diverse keys. Before coining new keys, recall() the topic and reuse returned canonical concepts or aliases. Semantically merged synonyms become aliases in one key cluster; shared broad keys become navigable hubs. CROSS-LINGUAL: add keys in both languages. namespace groups memories by project/context; ttl_seconds sets expiry; related_to adds explicit memory links; source attaches provenance and is auto-stamped with the server session, a timestamp, and — when a host agent (Claude Code, Codex) transcript is active — host_session/host_agent/host_turn so the memory can be traced back to its original conversation via get_conversation.

NameTypeReqDescription
contentstringyes
key_typesobject
keysarrayyes
namespacestring
related_toarray
sourceobject
ttl_secondsnumber

No output schema declared.

No examples provided.

remember_batch ~56

Save multiple memories in one call. Each item: {content, keys, key_types?, namespace?, ttl_seconds?, related_to?}. Returns list of saved IDs. More efficient than multiple remember() calls.

NameTypeReqDescription
itemsarrayyes

No output schema declared.

No examples provided.

Common questions

What is the io.github.donggyun112/keymem MCP server?

io.github.donggyun112/keymem is an MCP server listed in the public MCP registry as io.github.donggyun112/keymem. Associative key-graph memory for LLM agents, recall by association, not vector similarity. This page covers its npm package (keymem).

Is the io.github.donggyun112/keymem MCP server safe to use?

io.github.donggyun112/keymem scores 76 out of 100 on VerifyMCP. We recorded 12 known advisories against it as of 21 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 io.github.donggyun112/keymem MCP server expose?

io.github.donggyun112/keymem exposes 11 tools: recall, read_key, read_memory, remember, correct, and 6 more. Their descriptions and schemas cost roughly 1,055 tokens of context every time the server is loaded.

Is the io.github.donggyun112/keymem MCP server still maintained?

io.github.donggyun112/keymem 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 io.github.donggyun112/keymem MCP server under?

io.github.donggyun112/keymem declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.