memory_import

6 registry entries were observed exposing a tool named memory_import — none of them flagged as a privileged capability.

Spelled memory_import, memory.import 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.

1. @nuzo/memory-mcpverified
   trust 85/100 · AMCP serverobserved 2026-08-15 · static extraction
   Local-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.
2. dvalincodeverified
   trust 85/100 · AMCP serverobserved 2026-08-17 · static extraction
   Deterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked.
3. audrey
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   Local-first biological memory for coding agents: recall, consolidation, and pre-action Guard checks.
4. @studiomeyer/local-memory-mcp
   trust 60/100 · BMCP serverobserved 2026-06-23 · static extraction
   Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys.
5. contextforge-mcp
   trust 60/100 · BMCP serverobserved 2026-08-12 · static extraction
   Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot.
6. io.github.shackleai/memory
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Persistent memory for AI coding tools. 11 tools for any MCP-compatible AI tool.

All indexed toolsSearch the registry for memory_import