mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes

The best live alternatives to mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes right now are mcp-registry/io.github.blackboxfoundry/livedatalink/usgs_earthquake_search, mcp-registry/io.github.pipeworx-io/science/get_earthquakes, mcp-registry/io.github.pipeworx-io/emsc/search_earthquakes, mcp-registry/io.github.rippermercs/terminalfeed/tf_earthquakes, mcp-registry/com.daedalmap/earthquakes/get_earthquake_events — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes itself is currently "healthy".

alternative	server
mcp-registry/io.github.blackboxfoundry/livedatalink/usgs_earthquake_search	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/science/get_earthquakes	io.github.pipeworx-io/science	live status →
mcp-registry/io.github.pipeworx-io/emsc/search_earthquakes	io.github.pipeworx-io/emsc	live status →
mcp-registry/io.github.rippermercs/terminalfeed/tf_earthquakes	io.github.RipperMercs/terminalfeed	live status →
mcp-registry/com.daedalmap/earthquakes/get_earthquake_events	com.daedalmap/earthquakes	live status →
mcp-registry/com.daedalmap/county-map/get_earthquake_events	com.daedalmap/county-map	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/usgs-earthquake	ai.intuitek.the-stall/the-stall	live status →
mcp-registry/com.olyport/earthquake/get_recent_earthquakes	com.olyport/earthquake	live status →
mcp-registry/io.tooloracle/insuranceoracle/earthquake_risk	io.tooloracle/insuranceoracle	live status →
mcp-registry/io.github.pipeworx-io/gdacs/events	io.github.pipeworx-io/gdacs	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/earthquake-intel	ai.intuitek.the-stall/the-stall	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/data_earthquakes	io.github.ColinHughes2121/gocreative-agent-api	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes?

mcp-registry/io.github.blackboxfoundry/livedatalink/usgs_earthquake_search is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/science/get_earthquakes, mcp-registry/io.github.pipeworx-io/emsc/search_earthquakes, mcp-registry/io.github.rippermercs/terminalfeed/tf_earthquakes, mcp-registry/com.daedalmap/earthquakes/get_earthquake_events. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes down right now?

mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fusgs-earthquakes%2Fcount_earthquakes.

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%2Fusgs-earthquakes%2Fcount_earthquakes or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/usgs-earthquakes/count_earthquakes.