io.github.YonasValentin/mcp-memory-graph
NPM · MCP-MEMORY-GRAPH
Local-first memory for Claude Code and any MCP client: hybrid search + knowledge graph, $0/token.
Available components
Last scanned (9 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 73 of 209 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to YonasValentin/mcp-memory-graph). View diagnostics → Pass
- License check failed: the license (PolyForm-Noncommercial-1.0.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 121 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8922 tokens (~174/item across 51 items; 51 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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 52 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.
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −2
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 22 Oct 26 0
- CVE-2026-114112 affects this package: high ▼ security
- CVE-2026-114113 affects this package: high ▼ security
- CVE-2026-114111 affects this package: high ▼ security
- GHSA-wq5f-xc86-pv6w no longer affects this package ▲ security
- GHSA-rgj7-g3m4-5g8c no longer affects this package ▲ security
- GHSA-f88m-g3jw-g9cj no longer affects this package ▲ security
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.80 → pass security
- 16 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Stability: unverified → 0.80 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ 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/mcp-memory-graph@2.10.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | YonasValentin/mcp-memory-graph |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/YonasValentin/mcp-memory-graph/.github/workflows/release.yml@refs/tags/v2.10.3 |
| Rekor log index | 2084853267 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bb14d422b8c04ef83f5b0cc0d41992e5ea65ea12fd6f78ece3aa3d14c02f13f105ca164c47e6f4dd6e1c345a5d87c7e79f34dc61d14f4d6df3743599c |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | CVE-2026-114113 | high | yes | |
| GHSA-rgj7-g3m4-5g8c | CVE-2026-114112 | high | yes | |
| GHSA-wq5f-xc86-pv6w | CVE-2026-114111 | high | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 209 packages
| Packages resolved | 209 |
|---|---|
| Deprecated | 2 |
| Stale | 72 |
| 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 →
vault_sync ~173
Sync an Obsidian vault to memory. Scans for markdown files, extracts frontmatter/tags/wiki-links, embeds content, and stores as searchable memories. Uses incremental sync based on file modification times.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_overlap | integer | – | Overlap between chunks in characters for context preservation |
| chunk_size | integer | – | Target chunk size in characters for large files (~4 chars per token) |
| exclude_patterns | array | – | Skip files matching these glob patterns (e.g., ["templates/**", "daily/**"]) |
| force | boolean | – | If true, re-sync all files regardless of modification time |
| include_patterns | array | – | Only sync files matching these glob patterns (e.g., ["notes/**", "projects/**"]) |
| vault_path | string | yes | Absolute path to the Obsidian vault directory |
No output schema declared.
No examples provided.
How do I install the io.github.YonasValentin/mcp-memory-graph server?
io.github.YonasValentin/mcp-memory-graph runs locally as an npm package, launched with npx -y mcp-memory-graph. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-memory-graph
claude mcp add yonasvalentin-mcp-memory-graph -- npx -y mcp-memory-graph
What is the io.github.YonasValentin/mcp-memory-graph server?
io.github.YonasValentin/mcp-memory-graph is listed in the public MCP registry as io.github.YonasValentin/mcp-memory-graph. Local-first memory for Claude Code and any MCP client: hybrid search + knowledge graph, $0/token. This page covers its npm package (mcp-memory-graph).
Is the io.github.YonasValentin/mcp-memory-graph server safe to use?
io.github.YonasValentin/mcp-memory-graph scores 81 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.YonasValentin/mcp-memory-graph server expose?
io.github.YonasValentin/mcp-memory-graph exposes 51 tools: memory_store, memory_search, memory_get, memory_update, memory_delete, and 46 more. Their descriptions and schemas cost roughly 8,705 tokens of context every time the server is loaded.
Is the io.github.YonasValentin/mcp-memory-graph server still maintained?
io.github.YonasValentin/mcp-memory-graph 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.YonasValentin/mcp-memory-graph server under?
io.github.YonasValentin/mcp-memory-graph declares the PolyForm-Noncommercial-1.0.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.