mcp-registry/com.olyport/earthquake/get_earthquakes_near / alternatives

Live alternatives to mcp-registry/com.olyport/earthquake/get_earthquakes_near

The best live alternatives to mcp-registry/com.olyport/earthquake/get_earthquakes_near right now are mcp-registry/io.github.soapyred/freightutils/nearest_airport, mcp-registry/io.github.pipeworx-io/geonames/get_nearby, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search, mcp-registry/io.github.pipeworx-io/foursquare/nearby_places — capability-matched and ranked by current reliability. mcp-registry/com.olyport/earthquake/get_earthquakes_near itself is currently "healthy".

alternativeserver
mcp-registry/io.github.soapyred/freightutils/nearest_airportio.github.SoapyRED/freightutilslive status →
mcp-registry/io.github.pipeworx-io/geonames/get_nearbyio.github.pipeworx-io/geonameslive status →
mcp-registry/work.latlng.mcp/latlng/find_nearby_placeswork.latlng.mcp/latlnglive status →
mcp-registry/io.github.vee3io/vee3/google-maps.nearby_searchio.github.Vee3io/vee3live status →
mcp-registry/io.github.pipeworx-io/foursquare/nearby_placesio.github.pipeworx-io/foursquarelive status →
mcp-registry/io.github.pipeworx-io/science/get_earthquakesio.github.pipeworx-io/sciencelive status →
mcp-registry/io.github.pipeworx-io/predicthq/nearby_eventsio.github.pipeworx-io/predicthqlive status →
mcp-registry/com.olyport/ejscreen/get_ej_data_by_locationcom.olyport/ejscreenlive status →
mcp-registry/io.github.pipeworx-io/transit-land/search_stopsio.github.pipeworx-io/transit-landlive status →
mcp-registry/io.github.pipeworx-io/emsc/search_earthquakesio.github.pipeworx-io/emsclive status →
mcp-registry/com.eventmatey.mcp/event-discovery/search_events_nearbycom.eventmatey.mcp/event-discoverylive status →
mcp-registry/io.github.blackboxfoundry/livedatalink/recreation_nearbyio.github.blackboxfoundry/livedatalinklive status →

FAQ

What is the best alternative to mcp-registry/com.olyport/earthquake/get_earthquakes_near?

mcp-registry/io.github.soapyred/freightutils/nearest_airport is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/geonames/get_nearby, mcp-registry/work.latlng.mcp/latlng/find_nearby_places, mcp-registry/io.github.vee3io/vee3/google-maps.nearby_search, mcp-registry/io.github.pipeworx-io/foursquare/nearby_places. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.olyport/earthquake/get_earthquakes_near down right now?

mcp-registry/com.olyport/earthquake/get_earthquakes_near's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.olyport%2Fearthquake%2Fget_earthquakes_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%2Fcom.olyport%2Fearthquake%2Fget_earthquakes_near or MCP find_alternatives. Check mcp-registry/com.olyport/earthquake/get_earthquakes_near's live status: https://glimind.com/tool/mcp-registry/com.olyport/earthquake/get_earthquakes_near.