memory_store
10 registry entries were observed exposing a tool named memory_store — none of them flagged as a privileged capability.
Spelled memory_store, memory.store 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.
- MCP serverobserved · static extractionPersistent memory + context layer for AI dev teams. 17 tools via MCP.
- MCP serverobserved · static extractionAll-in-one MCP server: GitHub, Git, Slack, web fetch, memory, and filesystem. Agent Mode opt-in.
- MCP serverobserved · static extractionStateful backend for AI agents: memory, watch, render, execute, and shared boards with digests.
- MCP serverobserved · static extractionStandards-based A2A hub. One MCP connection to thousands of agents, with shared persistent memory.
- MCP serverobserved · static extractionJapan business regulations, compliance, travel, protocols, memory — 10 knowledge domains, 23 tools.
- MCP serverobserved · static extractionAgent memory MCP server with provenance tracking, decay-weighted recall, and feedback loops.
- MCP serverobserved · static extraction18 tools: agent memory, API drift detection, and HMAC-signed trust receipts
- MCP serverobserved · static extractionUniversal memory runtime for AI agents — episodic, semantic, and procedural memory.
- MCP serverobserved · static extractionPersistent, agent-owned memory with encrypted storage and shared knowledge commons.
- MCP serverobserved · static extractionPersistent memory for AI coding tools. 11 tools for any MCP-compatible AI tool.