npm/memory-engineering-mcp/memory_engineering_memory / alternatives
npm/memory-engineering-mcp/memory_engineering_memoryThe best live alternatives to npm/memory-engineering-mcp/memory_engineering_memory right now are mcp-registry/io.github.lazymac2x/agent-memory/get_memory, mcp-registry/com.memxus/memxus/forget, mcp-registry/io.github.lazymac2x/agent-memory/delete_memory, mcp-registry/com.googleapis.container/mcp/update_cluster, mcp-registry/io.github.williamechevarria/hivelearn-mcp/get_member — capability-matched and ranked by current reliability. npm/memory-engineering-mcp/memory_engineering_memory itself is currently "unknown".
mcp-registry/io.github.lazymac2x/agent-memory/get_memory is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.memxus/memxus/forget, mcp-registry/io.github.lazymac2x/agent-memory/delete_memory, mcp-registry/com.googleapis.container/mcp/update_cluster, mcp-registry/io.github.williamechevarria/hivelearn-mcp/get_member. Glimind ranks alternatives by semantic similarity and live health.
npm/memory-engineering-mcp/memory_engineering_memory's current verdict is "unknown". See its live status and score at https://glimind.com/tool/npm%2Fmemory-engineering-mcp%2Fmemory_engineering_memory.
By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/npm%2Fmemory-engineering-mcp%2Fmemory_engineering_memory
or MCP find_alternatives. Check npm/memory-engineering-mcp/memory_engineering_memory's live status: https://glimind.com/tool/npm/memory-engineering-mcp/memory_engineering_memory.