memory_export

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

Spelled memory_export, memory.export 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. trust 85/100 · AMCP serverobserved · static extraction
    Local-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.
  2. trust 60/100 · BMCP serverobserved · static extraction
    Local-first biological memory for coding agents: recall, consolidation, and pre-action Guard checks.
  3. trust 60/100 · BMCP serverobserved · static extraction
    Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys.
  4. trust 60/100 · BMCP serverobserved · static extraction
    Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot.
  5. trust 60/100 · BMCP serverobserved · static extraction
    Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe
  6. trust 60/100 · BMCP serverobserved · static extraction
    Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.
  7. trust 60/100 · BMCP serverobserved · static extraction
    Persistent, agent-owned memory with encrypted storage and shared knowledge commons.
  8. trust 60/100 · BMCP serverobserved · static extraction
    Persistent layered memory for AI agents. SQLite FTS5, fact versioning, zero-cloud.
  9. trust 60/100 · BMCP serverobserved · static extraction
    Persistent memory for AI coding tools. 11 tools for any MCP-compatible AI tool.

All indexed toolsSearch the registry for memory_export