mcp-registry/io.github.redis/mcp-redis/hash_get / alternatives

Live alternatives to mcp-registry/io.github.redis/mcp-redis/hash_get

The best live alternatives to mcp-registry/io.github.redis/mcp-redis/hash_get right now are mcp-registry/io.tinyfn/tinyfn/get_values, mcp-registry/io.tinyfn/tinyfn/get_keys, mcp-registry/io.tinyfn/tinyfn/hash_all — capability-matched and ranked by current reliability. mcp-registry/io.github.redis/mcp-redis/hash_get itself is currently "unknown".

alternative	server
mcp-registry/io.tinyfn/tinyfn/get_values	io.tinyfn/tinyfn	live status →
mcp-registry/io.tinyfn/tinyfn/get_keys	io.tinyfn/tinyfn	live status →
mcp-registry/io.tinyfn/tinyfn/hash_all	io.tinyfn/tinyfn	live status →

FAQ

What is the best alternative to mcp-registry/io.github.redis/mcp-redis/hash_get?

mcp-registry/io.tinyfn/tinyfn/get_values is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.tinyfn/tinyfn/get_keys, mcp-registry/io.tinyfn/tinyfn/hash_all. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.redis/mcp-redis/hash_get down right now?

mcp-registry/io.github.redis/mcp-redis/hash_get's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.redis%2Fmcp-redis%2Fhash_get.

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.github.redis%2Fmcp-redis%2Fhash_get or MCP find_alternatives. Check mcp-registry/io.github.redis/mcp-redis/hash_get's live status: https://glimind.com/tool/mcp-registry/io.github.redis/mcp-redis/hash_get.