mcp-registry/io.github.kapoost/humanmcp/recall / alternatives

Live alternatives to mcp-registry/io.github.kapoost/humanmcp/recall

The best live alternatives to mcp-registry/io.github.kapoost/humanmcp/recall right now are mcp-registry/io.github.pipeworx-io/nvd/search_within, mcp-registry/io.github.pipeworx-io/arcgis-lorain/search_within, mcp-registry/io.github.pipeworx-io/pride/search_within, mcp-registry/io.github.pipeworx-io/pokemon/search_within, mcp-registry/io.github.pipeworx-io/pirate-weather/search_within — capability-matched and ranked by current reliability. mcp-registry/io.github.kapoost/humanmcp/recall itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/nvd/search_within	io.github.pipeworx-io/nvd	live status →
mcp-registry/io.github.pipeworx-io/arcgis-lorain/search_within	io.github.pipeworx-io/arcgis-lorain	live status →
mcp-registry/io.github.pipeworx-io/pride/search_within	io.github.pipeworx-io/pride	live status →
mcp-registry/io.github.pipeworx-io/pokemon/search_within	io.github.pipeworx-io/pokemon	live status →
mcp-registry/io.github.pipeworx-io/pirate-weather/search_within	io.github.pipeworx-io/pirate-weather	live status →
mcp-registry/io.github.pipeworx-io/patents/search_within	io.github.pipeworx-io/patents	live status →
mcp-registry/io.github.pipeworx-io/peeringdb/search_within	io.github.pipeworx-io/peeringdb	live status →
mcp-registry/io.github.pipeworx-io/paleobiodb/search_within	io.github.pipeworx-io/paleobiodb	live status →
mcp-registry/io.github.pipeworx-io/outlook-mail/search_within	io.github.pipeworx-io/outlook-mail	live status →
mcp-registry/io.github.pipeworx-io/opendatasoft/search_within	io.github.pipeworx-io/opendatasoft	live status →
mcp-registry/io.github.pipeworx-io/opendota/search_within	io.github.pipeworx-io/opendota	live status →
mcp-registry/io.github.pipeworx-io/data-baltimore/search_within	io.github.pipeworx-io/data-baltimore	live status →

FAQ

What is the best alternative to mcp-registry/io.github.kapoost/humanmcp/recall?

mcp-registry/io.github.pipeworx-io/nvd/search_within is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/arcgis-lorain/search_within, mcp-registry/io.github.pipeworx-io/pride/search_within, mcp-registry/io.github.pipeworx-io/pokemon/search_within, mcp-registry/io.github.pipeworx-io/pirate-weather/search_within. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.kapoost/humanmcp/recall down right now?

mcp-registry/io.github.kapoost/humanmcp/recall's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.kapoost%2Fhumanmcp%2Frecall.

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.kapoost%2Fhumanmcp%2Frecall or MCP find_alternatives. Check mcp-registry/io.github.kapoost/humanmcp/recall's live status: https://glimind.com/tool/mcp-registry/io.github.kapoost/humanmcp/recall.