mcp · handle optchat
mem0_mcp_selfhosted · job 77%MemU MCP Server · job 79%monomind · job 74%pseudolife_mcp · job 78%mcp_memory_keeper · job 75%Khwan MCP · job 77%Obsidiyan Engine · job 79%recallnest · job 78%engram_5 · job 75%Escritório · job 77%session-hub · job 79%agentbus · job 73%remem · job 79%one_brain · job 80%RelayHistory · job 75%commonplace · job 83%memorix · job 80%sirro · job 80%agent-peers · job 74%Mindtrail · job 77%Mneme · job 73%Claude Context Hub · job 81%MCP Memory Server · job 77%knowledge-commons · job 84%mem-rfm · job 76%sigma-mem · job 76%agent_memguard · job 78%linklore · job 78%MCP KB SQLite · job 80%claude_memory_mcp_2 · job 86%DeepMem · job 75%Task Journal · job 79%wormhole_mcp · job 77%KMP · job 81%MemHub · job 79%threadctx · job 75%Terraforma Memory · job 77%Engram · job 78%Knos · job 75%magents · job 77%jevmem · job 81%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series