npm/codemem/memory_stats / alternatives

Live alternatives to npm/codemem/memory_stats

The best live alternatives to npm/codemem/memory_stats right now are mcp-registry/com.memxus/memxus/memory_stats, mcp-registry/io.github.pkaldone/substrate/memory_stats, mcp-registry/io.tooloracle/memoryoracle/memory_stats — capability-matched and ranked by current reliability. npm/codemem/memory_stats itself is currently "unknown".

alternative	server
mcp-registry/com.memxus/memxus/memory_stats	com.memxus/memxus	live status →
mcp-registry/io.github.pkaldone/substrate/memory_stats	io.github.PKaldone/substrate	live status →
mcp-registry/io.tooloracle/memoryoracle/memory_stats	io.tooloracle/memoryoracle	live status →

FAQ

What is the best alternative to npm/codemem/memory_stats?

mcp-registry/com.memxus/memxus/memory_stats is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pkaldone/substrate/memory_stats, mcp-registry/io.tooloracle/memoryoracle/memory_stats. Glimind ranks alternatives by semantic similarity and live health.

Is npm/codemem/memory_stats down right now?

npm/codemem/memory_stats's current verdict is "unknown". See its live status and score at https://glimind.com/tool/npm%2Fcodemem%2Fmemory_stats.

How does Glimind pick alternatives?

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.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/npm%2Fcodemem%2Fmemory_stats or MCP find_alternatives. Check npm/codemem/memory_stats's live status: https://glimind.com/tool/npm/codemem/memory_stats.