DuckDB Knowledge Graph MemorySAFE
MCP Memory Server with DuckDB backend
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://github.com/izumisy/mcp-duckdb-memory-server/actions/workflows/test.yaml) [](https://smithery.ai/server/@IzumiSy/mcp-duckdb-memory-server)
A forked version of the official Knowledge Graph Memory Server.
Installation
Installing via Smithery
To install DuckDB Knowledge Graph Memory Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @IzumiSy/mcp-duckdb-memory-server --client claude
Manual install
Otherwise, add @IzumiSy/mcp-duckdb-memory-server in your claude_desktop_config.json manually (MEMORY_FILE_PATH is optional)
{
"mcpServers": {
"graph-memory": {
"command": "npx",
"args": [
"-y",
"@izumisy/mcp-duckdb-memory-server"
],
"env": {
"MEMORY_FILE_PATH": "/path/to/your/memory.data"
}
}
}
}The data stored on that path is a DuckDB database file.
Docker
Build
docker build -t mcp-duckdb-graph-memory .
Run
docker run -dit mcp-duckdb-graph-memory
Usage
Use the example instruction below
Follow these steps for each interaction: 1. User Identification: - You should assume that you are interacting with default_user - If you have not identified default_user,
cce315cadb8cOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-duckdb-memory-server -- npx -y @izumisy/[email protected]
{
"mcpServers": {
"mcp-duckdb-memory-server": {
"command": "npx",
"args": [
"-y",
"@izumisy/[email protected]"
]
}
}
}Exposed tools (8)
2 read · 3 write · 3 destructive. Blast radius: 3 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
add_observations | write | Add new observations to existing entities in the knowledge graph |
create_entities | write | Create multiple new entities in the knowledge graph |
create_relations | write | Create multiple new relations between entities in the knowledge graph. Relations should be in active voice |
delete_entities | destructive | Delete multiple entities and their associated relations from the knowledge graph |
delete_observations | destructive | Delete specific observations from entities in the knowledge graph |
delete_relations | destructive | Delete multiple relations from the knowledge graph |
open_nodes | read | Open specific nodes in the knowledge graph by their names |
search_nodes | read | Search for nodes in the knowledge graph based on a query |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
delete_entities, delete_observations, delete_relations
@modelcontextprotocol/sdk, fuse.js, zod, @cfworker/json-schema, @changesets/cli, @swc/core, @types/node, prettier
Always begin your chat by saying only "Remembering..." and search relevant information from your knowledge graph
Gates applied: no_behavioural_pass.
cce315cadb8cfull audit observations/trust-audit/mcp-server/izumisy__duckdb-knowledge-graph-memory.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | cce315cadb8c | SAFE | B | 89 | first audit |
Questions
What is the DuckDB Knowledge Graph Memory MCP server?
MCP Memory Server with DuckDB backend
What tools does DuckDB Knowledge Graph Memory expose?
8 in total: 2 read-only, 3 that write, and 3 that can delete or overwrite (delete_entities, delete_observations, delete_relations). Every one is listed on this page with its risk.
Is DuckDB Knowledge Graph Memory safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 3 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does DuckDB Knowledge Graph Memory need?
No credential environment variables were found in its source, so it appears to need none.
How does DuckDB Knowledge Graph Memory run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @izumisy/mcp-duckdb-memory-server at 1.1.10.
How current is this page?
The grade is for one exact copy of the source (cce315cadb8c), read on 2026-10-08. The repository is watched and re-audited when it changes.