mcp-registry/io.github.pipeworx-io/lichess/recall / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/lichess/recall

The best live alternatives to mcp-registry/io.github.pipeworx-io/lichess/recall right now are mcp-registry/io.github.pipeworx-io/webflow/entity_profile, mcp-registry/io.github.pipeworx-io/data-montgomery/entity_profile, mcp-registry/io.github.pipeworx-io/data-denver/entity_profile, mcp-registry/io.github.pipeworx-io/dummyjson/entity_profile, mcp-registry/io.github.pipeworx-io/datagov-uk/entity_profile — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/lichess/recall itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/webflow/entity_profile	io.github.pipeworx-io/webflow	live status →
mcp-registry/io.github.pipeworx-io/data-montgomery/entity_profile	io.github.pipeworx-io/data-montgomery	live status →
mcp-registry/io.github.pipeworx-io/data-denver/entity_profile	io.github.pipeworx-io/data-denver	live status →
mcp-registry/io.github.pipeworx-io/dummyjson/entity_profile	io.github.pipeworx-io/dummyjson	live status →
mcp-registry/io.github.pipeworx-io/datagov-uk/entity_profile	io.github.pipeworx-io/datagov-uk	live status →
mcp-registry/io.github.pipeworx-io/bioregistry/entity_profile	io.github.pipeworx-io/bioregistry	live status →
mcp-registry/io.github.pipeworx-io/banxico/entity_profile	io.github.pipeworx-io/banxico	live status →
mcp-registry/io.github.pipeworx-io/bank-of-canada/entity_profile	io.github.pipeworx-io/bank-of-canada	live status →
mcp-registry/io.github.pipeworx-io/barcelona-events/entity_profile	io.github.pipeworx-io/barcelona-events	live status →
mcp-registry/io.github.pipeworx-io/attom/entity_profile	io.github.pipeworx-io/attom	live status →
mcp-registry/io.github.pipeworx-io/avoindata-fi/entity_profile	io.github.pipeworx-io/avoindata-fi	live status →
mcp-registry/io.github.pipeworx-io/arxiv/entity_profile	io.github.pipeworx-io/arxiv	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/lichess/recall?

mcp-registry/io.github.pipeworx-io/webflow/entity_profile is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/data-montgomery/entity_profile, mcp-registry/io.github.pipeworx-io/data-denver/entity_profile, mcp-registry/io.github.pipeworx-io/dummyjson/entity_profile, mcp-registry/io.github.pipeworx-io/datagov-uk/entity_profile. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/lichess/recall down right now?

mcp-registry/io.github.pipeworx-io/lichess/recall's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Flichess%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.pipeworx-io%2Flichess%2Frecall or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/lichess/recall's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/lichess/recall.