mcp-registry/io.github.pipeworx-io/madrid-events/recall / alternatives

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

The best live alternatives to mcp-registry/io.github.pipeworx-io/madrid-events/recall right now are mcp-registry/io.github.pipeworx-io/fcc/recall, mcp-registry/io.github.pipeworx-io/fbi-wanted/recall, mcp-registry/io.github.pipeworx-io/arcgis-maricopa/recall, mcp-registry/io.github.pipeworx-io/owid/recall, mcp-registry/io.github.pipeworx-io/fas/recall — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/madrid-events/recall itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/fcc/recall	io.github.pipeworx-io/fcc	live status →
mcp-registry/io.github.pipeworx-io/fbi-wanted/recall	io.github.pipeworx-io/fbi-wanted	live status →
mcp-registry/io.github.pipeworx-io/arcgis-maricopa/recall	io.github.pipeworx-io/arcgis-maricopa	live status →
mcp-registry/io.github.pipeworx-io/owid/recall	io.github.pipeworx-io/owid	live status →
mcp-registry/io.github.pipeworx-io/fas/recall	io.github.pipeworx-io/fas	live status →
mcp-registry/io.github.pipeworx-io/stooq/recall	io.github.pipeworx-io/stooq	live status →
mcp-registry/io.github.pipeworx-io/pypi/recall	io.github.pipeworx-io/pypi	live status →
mcp-registry/io.github.pipeworx-io/librivox/recall	io.github.pipeworx-io/librivox	live status →
mcp-registry/io.github.pipeworx-io/openstates/recall	io.github.pipeworx-io/openstates	live status →
mcp-registry/io.github.pipeworx-io/yc-rejection/recall	io.github.pipeworx-io/yc-rejection	live status →
mcp-registry/io.github.pipeworx-io/carbon-interface/recall	io.github.pipeworx-io/carbon-interface	live status →
mcp-registry/io.github.pipeworx-io/endoflife/recall	io.github.pipeworx-io/endoflife	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/fcc/recall is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/fbi-wanted/recall, mcp-registry/io.github.pipeworx-io/arcgis-maricopa/recall, mcp-registry/io.github.pipeworx-io/owid/recall, mcp-registry/io.github.pipeworx-io/fas/recall. Glimind ranks alternatives by semantic similarity and live health.

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

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