mcp-registry/io.github.dynamitecircle/dc/places_search / alternatives

Live alternatives to mcp-registry/io.github.dynamitecircle/dc/places_search

The best live alternatives to mcp-registry/io.github.dynamitecircle/dc/places_search right now are mcp-registry/io.github.vee3io/vee3/google-maps.search, mcp-registry/work.latlng.mcp/latlng/search_places, mcp-registry/io.github.vee3io/vee3/google-maps.place_types, mcp-registry/io.github.pipeworx-io/google_maps/maps_place_details, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search — capability-matched and ranked by current reliability. mcp-registry/io.github.dynamitecircle/dc/places_search itself is currently "healthy".

alternative	server
mcp-registry/io.github.vee3io/vee3/google-maps.search	io.github.Vee3io/vee3	live status →
mcp-registry/work.latlng.mcp/latlng/search_places	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.place_types	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_place_details	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search	io.github.Vee3io/vee3	live status →
mcp-registry/com.googleapis.mapstools/mcp/search_places	com.googleapis.mapstools/mcp	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.place_details	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.pipeworx-io/serper/places	io.github.pipeworx-io/serper	live status →
mcp-registry/app.zooza/mcp-server/classes_find_places	app.zooza/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/setlist-fm/venue_search	io.github.pipeworx-io/setlist-fm	live status →
mcp-registry/io.github.pipeworx-io/google_maps/maps_place_search	io.github.pipeworx-io/google_maps	live status →
mcp-registry/io.github.pipeworx-io/foursquare/search_places	io.github.pipeworx-io/foursquare	live status →

FAQ

What is the best alternative to mcp-registry/io.github.dynamitecircle/dc/places_search?

mcp-registry/io.github.vee3io/vee3/google-maps.search is the top capability-matched alternative that's live right now. Other options: mcp-registry/work.latlng.mcp/latlng/search_places, mcp-registry/io.github.vee3io/vee3/google-maps.place_types, mcp-registry/io.github.pipeworx-io/google_maps/maps_place_details, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.dynamitecircle/dc/places_search down right now?

mcp-registry/io.github.dynamitecircle/dc/places_search's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.dynamitecircle%2Fdc%2Fplaces_search.

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.dynamitecircle%2Fdc%2Fplaces_search or MCP find_alternatives. Check mcp-registry/io.github.dynamitecircle/dc/places_search's live status: https://glimind.com/tool/mcp-registry/io.github.dynamitecircle/dc/places_search.