npm/-memlink/cli/memory_read / alternatives
npm/-memlink/cli/memory_readThe best live alternatives to npm/-memlink/cli/memory_read right now are mcp-registry/io.github.lazymac2x/agent-memory/get_memory, mcp-registry/io.github.lazymac2x/agent-memory/delete_memory, mcp-registry/com.memxus/memxus/forget, mcp-registry/io.github.pipeworx-io/rfc-editor/rfc_metadata, mcp-registry/io.tooloracle/leadoracle/industry_companies — capability-matched and ranked by current reliability. npm/-memlink/cli/memory_read 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/io.github.lazymac2x/agent-memory/delete_memory, mcp-registry/com.memxus/memxus/forget, mcp-registry/io.github.pipeworx-io/rfc-editor/rfc_metadata, mcp-registry/io.tooloracle/leadoracle/industry_companies. Glimind ranks alternatives by semantic similarity and live health.
npm/-memlink/cli/memory_read's current verdict is "unknown". See its live status and score at https://glimind.com/tool/npm%2F-memlink%2Fcli%2Fmemory_read.
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%2F-memlink%2Fcli%2Fmemory_read
or MCP find_alternatives. Check npm/-memlink/cli/memory_read's live status: https://glimind.com/tool/npm/-memlink/cli/memory_read.