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…
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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 graphCreate 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 voiceCreate 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 graphAdd 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 graphDelete 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 graphDelete specific observations from entities in the knowledge graph
No input schema was published for this tool.
delete_relationsprivilegedDelete multiple relations from the knowledge graphDelete multiple relations from the knowledge graph
No input schema was published for this tool.
read_graphRead the entire knowledge graphRead the entire knowledge graph
No input schema was published for this tool.
search_nodesSearch for nodes in the knowledge graph based on a querySearch 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 namesOpen 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.
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
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
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)
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.