memory_write
9 registry entries were observed exposing a tool named memory_write — 9 of them as a privileged capability (a name matching exec / write / delete keywords).
Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.
- MCP serverobserved · static extractionPersistent, verified memory for AI coding agents. CLI: dim.
- MCP serverobserved · static extractionDeterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked.
- MCP serverobserved · static extractionOpen, Git-native memory protocol for MCP agents. Portable, versioned, human-editable.
- @mnemoverse/mcp-memory-serverprivilegedMCP serverobserved · static extractionHosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT.
- dev.gnosem/gnosemprivilegedMCP serverobserved · static extractionCross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
- io.github.Lore-Context/lore-context-mcpprivilegedMCP serverobserved · static extractionGoverned AI-agent memory, Evidence Ledger traces, evals, and portable context tools.
- MCP serverobserved · static extractionPersistent memory for AI agents across Claude, ChatGPT and any MCP client.
- sthayiprivilegedMCP serverobserved · static extractionLocal-first AI memory over MCP. No account; you own the store.
- threadctx-mcpprivilegedMCP serverobserved · static extractionShared memory MCP server for AI coding agents — local by default, team-shared via threadctx.dev.