mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory / alternatives

Live alternatives to mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory

The best live alternatives to mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory right now are mcp-registry/ai.thinkneo/control-plane/thinkneo_read_memory, mcp-registry/com.babyblueviper/invinoveritas/memory_list, mcp-registry/io.github.synapselayer/synapse-layer/list_memories, mcp-registry/io.github.cleanslice/mcp/read-doc, mcp-registry/io.github.vortx-ai/emem/memory_list_by_kind — capability-matched and ranked by current reliability. mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory itself is currently "healthy".

alternativeserver
mcp-registry/ai.thinkneo/control-plane/thinkneo_read_memoryai.thinkneo/control-planelive status →
mcp-registry/com.babyblueviper/invinoveritas/memory_listcom.babyblueviper/invinoveritaslive status →
mcp-registry/io.github.synapselayer/synapse-layer/list_memoriesio.github.SynapseLayer/synapse-layerlive status →
mcp-registry/io.github.cleanslice/mcp/read-docio.github.CleanSlice/mcplive status →
mcp-registry/io.github.vortx-ai/emem/memory_list_by_kindio.github.Vortx-AI/ememlive status →
mcp-registry/io.github.seunghan91/ainote/memory_getio.github.seunghan91/ainotelive status →
mcp-registry/com.myagentinbox/myagentinbox/read_messagecom.myagentinbox/myagentinboxlive status →
mcp-registry/io.github.xgr-network/xdala-workflow-builder/read_xrc137_rule_jsonio.github.xgr-network/xdala-workflow-builderlive status →
mcp-registry/com.wingmanprotocol.agent/gateway/memory_statscom.wingmanprotocol.agent/gatewaylive status →
mcp-registry/io.github.vortx-ai/emem/memory_deleteio.github.Vortx-AI/ememlive status →
mcp-registry/io.github.lazymac2x/agent-memory/get_memoryio.github.lazymac2x/agent-memorylive status →
mcp-registry/be.vibedeploy/vibedeploy/read_filesbe.vibedeploy/vibedeploylive status →

FAQ

What is the best alternative to mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory?

mcp-registry/ai.thinkneo/control-plane/thinkneo_read_memory is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.babyblueviper/invinoveritas/memory_list, mcp-registry/io.github.synapselayer/synapse-layer/list_memories, mcp-registry/io.github.cleanslice/mcp/read-doc, mcp-registry/io.github.vortx-ai/emem/memory_list_by_kind. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory down right now?

mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.pathrule%2Fpathrule-remote-mcp%2Fpathrule_read_memory.

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/mcp-registry%2Fio.pathrule%2Fpathrule-remote-mcp%2Fpathrule_read_memory or MCP find_alternatives. Check mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory's live status: https://glimind.com/tool/mcp-registry/io.pathrule/pathrule-remote-mcp/pathrule_read_memory.