mcp-registry/io.github.pipeworx-io/predicthq/nearby_events / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/predicthq/nearby_events

The best live alternatives to mcp-registry/io.github.pipeworx-io/predicthq/nearby_events right now are mcp-registry/com.eventmatey.mcp/event-discovery/search_events_nearby, mcp-registry/io.github.pipeworx-io/edmtrain/events, mcp-registry/io.github.pipeworx-io/foursquare/nearby_places, mcp-registry/io.github.pipeworx-io/geonames/get_nearby, mcp-registry/work.latlng.mcp/latlng/find_nearby_places — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/predicthq/nearby_events itself is currently "healthy".

alternative	server
mcp-registry/com.eventmatey.mcp/event-discovery/search_events_nearby	com.eventmatey.mcp/event-discovery	live status →
mcp-registry/io.github.pipeworx-io/edmtrain/events	io.github.pipeworx-io/edmtrain	live status →
mcp-registry/io.github.pipeworx-io/foursquare/nearby_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.pipeworx-io/geonames/get_nearby	io.github.pipeworx-io/geonames	live status →
mcp-registry/work.latlng.mcp/latlng/find_nearby_places	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.pipeworx-io/ebird/nearby_observations	io.github.pipeworx-io/ebird	live status →
mcp-registry/com.lodikidsactivities/lodi-kids-activities/nearby_programs	com.lodikidsactivities/lodi-kids-activities	live status →
mcp-registry/io.github.pipeworx-io/gbif/occurrences_near	io.github.pipeworx-io/gbif	live status →
mcp-registry/io.github.pipeworx-io/geoapify/places	io.github.pipeworx-io/geoapify	live status →
mcp-registry/io.github.pipeworx-io/skiddle/search_events	io.github.pipeworx-io/skiddle	live status →
mcp-registry/io.github.pipeworx-io/19hz/events	io.github.pipeworx-io/19hz	live status →
pulsemcp/19hz-events/events	19hz Events	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/predicthq/nearby_events?

mcp-registry/com.eventmatey.mcp/event-discovery/search_events_nearby is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/edmtrain/events, mcp-registry/io.github.pipeworx-io/foursquare/nearby_places, mcp-registry/io.github.pipeworx-io/geonames/get_nearby, mcp-registry/work.latlng.mcp/latlng/find_nearby_places. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/predicthq/nearby_events down right now?

mcp-registry/io.github.pipeworx-io/predicthq/nearby_events's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fpredicthq%2Fnearby_events.

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%2Fpredicthq%2Fnearby_events or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/predicthq/nearby_events's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/predicthq/nearby_events.