@modelcontextprotocol/server-memory

MCPattested
v2026.1.26Anthropic, PBCMITUpdated 8mo agonpmGitHub

MCP server for enabling memory for Claude through a knowledge graph

A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats. 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 Example: Relations define directed connections between entities. They…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
86kGitHub stars
11kForks
8mo agoLast update
Package
AuthorAnthropic, PBC
LicenseMIT
Version2026.1.26
Sourcenpm+github
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 7097923
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · 3 privileged
Security scan✓ Cleanv2026.7.4 · 1mo agoHow well does this scan work?
EvalsNone
IndexedMay 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · 3 privileged
Statically extracted from the published packagev2026.7.4 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

create_entitiesCreate multiple new entities in the knowledge graph

Create multiple new entities in the knowledge graph

No input schema was published for this tool.

create_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voice

Create multiple new relations between entities in the knowledge graph. Relations should be in active voice

No input schema was published for this tool.

add_observationsAdd new observations to existing entities in the knowledge graph

Add new observations to existing entities in the knowledge graph

No input schema was published for this tool.

delete_entitiesprivilegedDelete multiple entities and their associated relations from the knowledge graph

Delete multiple entities and their associated relations from the knowledge graph

No input schema was published for this tool.

delete_observationsprivilegedDelete specific observations from entities in the knowledge graph

Delete specific observations from entities in the knowledge graph

No input schema was published for this tool.

delete_relationsprivilegedDelete multiple relations from the knowledge graph

Delete multiple relations from the knowledge graph

No input schema was published for this tool.

read_graphRead the entire knowledge graph

Read the entire knowledge graph

No input schema was published for this tool.

search_nodesSearch for nodes in the knowledge graph based on a query

Search for nodes in the knowledge graph based on a query

No input schema was published for this tool.

open_nodesOpen specific nodes in the knowledge graph by their names

Open specific nodes in the knowledge graph by their names

No input schema was published for this tool.

9 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats. 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 Example: Relations define directed connections between entities. They are always stored in active voice and describe how entities interact or relate to each other. Examp

Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-28 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in memory & knowledge graphs