mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues / alternatives

Live alternatives to mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues

The best live alternatives to mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues right now are mcp-registry/io.github.dynamitecircle/dc/places_search, mcp-registry/me.foodnear/foodnear-me/search_restaurants, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search, mcp-registry/team.jogo/mcp/get_venue, mcp-registry/com.agentorist/agentorist/list_venues — capability-matched and ranked by current reliability. mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues itself is currently "healthy".

alternativeserver
mcp-registry/io.github.dynamitecircle/dc/places_searchio.github.dynamitecircle/dclive status →
mcp-registry/me.foodnear/foodnear-me/search_restaurantsme.foodnear/foodnear-melive status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_searchio.github.Vee3io/vee3live status →
mcp-registry/team.jogo/mcp/get_venueteam.jogo/mcplive status →
mcp-registry/com.agentorist/agentorist/list_venuescom.agentorist/agentoristlive status →
mcp-registry/io.github.pipeworx-io/foursquare/search_placesio.github.pipeworx-io/foursquarelive status →
mcp-registry/app.zooza/mcp-server/classes_find_placesapp.zooza/mcp-serverlive status →
mcp-registry/io.github.pipeworx-io/geoapify/placesio.github.pipeworx-io/geoapifylive status →
mcp-registry/io.github.pipeworx-io/openrouteservice/geocode_searchio.github.pipeworx-io/openrouteservicelive status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_place_searchio.github.pipeworx-io/google_mapslive status →
mcp-registry/dev.workers.lionmaster-operations.lion-x402/lion-x402/lion_poi_business_searchdev.workers.lionmaster-operations.lion-x402/lion-x402live status →
mcp-registry/com.lionx402/lion-x402/lion_poi_business_searchcom.lionx402/lion-x402live status →

FAQ

What is the best alternative to mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues?

mcp-registry/io.github.dynamitecircle/dc/places_search is the top capability-matched alternative that's live right now. Other options: mcp-registry/me.foodnear/foodnear-me/search_restaurants, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search, mcp-registry/team.jogo/mcp/get_venue, mcp-registry/com.agentorist/agentorist/list_venues. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues down right now?

mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.luisa-sys%2Flyra-mcp-server%2Flyra_suggest_venues.

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.luisa-sys%2Flyra-mcp-server%2Flyra_suggest_venues or MCP find_alternatives. Check mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues's live status: https://glimind.com/tool/mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_suggest_venues.