mcp-registry/io.github.pipeworx-io/gbif/occurrences_near / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/gbif/occurrences_near

The best live alternatives to mcp-registry/io.github.pipeworx-io/gbif/occurrences_near right now are mcp-registry/io.github.pipeworx-io/ebird/nearby_observations, mcp-registry/ai.dynamicfeed/dynamic-feed/species_occurrences, mcp-registry/io.github.pipeworx-io/obis/find_occurrences, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.pipeworx-io/geonames/get_nearby — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/gbif/occurrences_near itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/ebird/nearby_observations	io.github.pipeworx-io/ebird	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/species_occurrences	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.pipeworx-io/obis/find_occurrences	io.github.pipeworx-io/obis	live status →
mcp-registry/work.latlng.mcp/latlng/find_nearby_places	work.latlng.mcp/latlng	live status →
mcp-registry/io.github.pipeworx-io/geonames/get_nearby	io.github.pipeworx-io/geonames	live status →
mcp-registry/io.github.pipeworx-io/predicthq/nearby_events	io.github.pipeworx-io/predicthq	live status →
mcp-registry/io.github.pipeworx-io/foursquare/nearby_places	io.github.pipeworx-io/foursquare	live status →
mcp-registry/io.github.pipeworx-io/inaturalist/search_observations	io.github.pipeworx-io/inaturalist	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/recreation_nearby	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.tickadoo/tickadoo-mcp/find_nearby_experiences	io.github.tickadoo/tickadoo-mcp	live status →
mcp-registry/io.github.pipeworx-io/geonames/search_geonames	io.github.pipeworx-io/geonames	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/gbif/occurrences_near?

mcp-registry/io.github.pipeworx-io/ebird/nearby_observations is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.dynamicfeed/dynamic-feed/species_occurrences, mcp-registry/io.github.pipeworx-io/obis/find_occurrences, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.pipeworx-io/geonames/get_nearby. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/gbif/occurrences_near down right now?

mcp-registry/io.github.pipeworx-io/gbif/occurrences_near's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fgbif%2Foccurrences_near.

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%2Fgbif%2Foccurrences_near or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/gbif/occurrences_near's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/gbif/occurrences_near.