Knowledge Graph MemorySAFE
MCP server enabling persistent memory for Claude through a local knowledge graph - fork focused on local development
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://smithery.ai/server/@itseasy21/mcp-knowledge-graph)
An improved implementation of persistent memory using a local knowledge graph with a customizable memory path.
This lets Claude remember information about the user across chats.
[!NOTE] This is a fork of the original Memory Server and is intended to not use the ephemeral memory npx installation method.
Server Name
mcp-knowledge-graph
Core Concepts
Entities
Entities are the primary nodes in the knowledge graph. Each entity has:
- A unique name (identifier)
- An entity type (e.g., "person", "organization", "event")
- A list of observations
- Creation date and version tracking
The version tracking feature helps maintain a historical context of how knowledge evolves over time.
Example:
{
"name": "John_Smith",
"entityType": "person",
"observations": ["Speaks fluent Spanish"]
}Relations
Relations define directed connections between entities. They are always stored in active voice and describe how entities interact or relate to each other. Each relation includes:
- Source and target entities
- Relationship type
- Creation date and version information
This versioning system helps track how relationships between entities evolve over time.
Example:
{
"from": "John_Smith",
"to": "Anthropic",
"relationType": "works_at"
}Observations
Observations are discrete pieces of information about an entity. They are:
- Stored as strings
- Attached
3385c2cd0722OBSERVED · 2026-10-07Connect
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-knowledge-graph -- npx -y @itseasy21/[email protected]
{
"mcpServers": {
"mcp-knowledge-graph": {
"command": "npx",
"args": [
"-y",
"@itseasy21/[email protected]"
]
}
}
}Exposed tools (11)
3 read · 5 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 |
read_graph | read | Read the entire knowledge graph |
search_nodes | read | Search for nodes in the knowledge graph based on a query |
update_entities | write | Update multiple existing entities in the knowledge graph |
update_relations | write | Update multiple existing relations in the knowledge graph |
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 (2)
delete_entities, delete_observations, delete_relations
minimist, @types/minimist, @types/node, shx, typescript
Gates applied: no_behavioural_pass.
3385c2cd0722full audit observations/trust-audit/mcp-server/itseasy21__knowledge-graph-memory-1.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-07 | 3385c2cd0722 | SAFE | B | 89 | first audit |
Questions
What is the Knowledge Graph Memory MCP server?
MCP server enabling persistent memory for Claude through a local knowledge graph - fork focused on local development
What tools does Knowledge Graph Memory expose?
11 in total: 3 read-only, 5 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 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 Knowledge Graph Memory need?
No credential environment variables were found in its source, so it appears to need none.
How does Knowledge Graph Memory run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @itseasy21/mcp-knowledge-graph at 1.0.7.
How current is this page?
The grade is for one exact copy of the source (3385c2cd0722), read on 2026-10-07. The repository is watched and re-audited when it changes.