memory_update
11 registry entries were observed exposing a tool named memory_update — none of them flagged as a privileged capability.
Spelled memory_update, memory.update in the wild — all one tool for the purposes of this page.
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.
- @nuzo/memory-mcpverifiedMCP serverobserved · static extractionLocal-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.
- dvalincodeverifiedMCP serverobserved · static extractionDeterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked.
- io.github.amenophis1er/elefanteverifiedMCP serverobserved · static extractionOpen, Git-native memory protocol for MCP agents. Portable, versioned, human-editable.
- MCP serverobserved · static extractionLong-term memory for Claude Code, Cursor and any MCP client, with a searchable web dashboard.
- MCP serverobserved · static extractionPersistent memory + context layer for AI dev teams. 17 tools via MCP.
- MCP serverobserved · static extractionLong-term memory for Claude Code with SQLite FTS5 search and BM25 ranking
- MCP serverobserved · static extractionGoverned AI-agent memory, Evidence Ledger traces, evals, and portable context tools.
- MCP serverobserved · static extraction18 tools: agent memory, API drift detection, and HMAC-signed trust receipts
- MCP serverobserved · static extractionAI that remembers. Local-first cross-session, cross-project long-term memory for coding tools.
- MCP serverobserved · static extractionPersistent layered memory for AI agents. SQLite FTS5, fact versioning, zero-cloud.
- MCP serverobserved · static extractionPersistent memory for AI coding tools. 11 tools for any MCP-compatible AI tool.