mcp-registry/io.github.vortx-ai/emem/emem_lst / alternatives

Live alternatives to mcp-registry/io.github.vortx-ai/emem/emem_lst

The best live alternatives to mcp-registry/io.github.vortx-ai/emem/emem_lst right now are mcp-registry/io.github.pipeworx-io/gistemp/get_temperature_anomaly, mcp-registry/io.github.pipeworx-io/nws/get_forecast, mcp-registry/io.github.mcflamingo/local-intel/local_intel_tide, mcp-registry/ai.dynamicfeed/dynamic-feed/ephemeris, mcp-registry/io.github.pipeworx-io/cdec-ca/daily_data — capability-matched and ranked by current reliability. mcp-registry/io.github.vortx-ai/emem/emem_lst itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/gistemp/get_temperature_anomaly	io.github.pipeworx-io/gistemp	live status →
mcp-registry/io.github.pipeworx-io/nws/get_forecast	io.github.pipeworx-io/nws	live status →
mcp-registry/io.github.mcflamingo/local-intel/local_intel_tide	io.github.MCFLAMINGO/local-intel	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/ephemeris	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.pipeworx-io/cdec-ca/daily_data	io.github.pipeworx-io/cdec-ca	live status →
mcp-registry/io.github.pipeworx-io/gistemp/get_latest_anomaly	io.github.pipeworx-io/gistemp	live status →
mcp-registry/app.nausika/mcp/nausika_marine_forecast	app.nausika/mcp	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/sst_anomaly	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.pipeworx-io/noaa-spc/convective_outlook	io.github.pipeworx-io/noaa-spc	live status →
mcp-registry/io.github.pipeworx-io/noaa-tides/met_obs	io.github.pipeworx-io/noaa-tides	live status →
mcp-registry/io.github.pipeworx-io/open-meteo/historical	io.github.pipeworx-io/open-meteo	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/weather-history	ai.intuitek.the-stall/the-stall	live status →

FAQ

What is the best alternative to mcp-registry/io.github.vortx-ai/emem/emem_lst?

mcp-registry/io.github.pipeworx-io/gistemp/get_temperature_anomaly is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/nws/get_forecast, mcp-registry/io.github.mcflamingo/local-intel/local_intel_tide, mcp-registry/ai.dynamicfeed/dynamic-feed/ephemeris, mcp-registry/io.github.pipeworx-io/cdec-ca/daily_data. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.vortx-ai/emem/emem_lst down right now?

mcp-registry/io.github.vortx-ai/emem/emem_lst's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.vortx-ai%2Femem%2Femem_lst.

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.vortx-ai%2Femem%2Femem_lst or MCP find_alternatives. Check mcp-registry/io.github.vortx-ai/emem/emem_lst's live status: https://glimind.com/tool/mcp-registry/io.github.vortx-ai/emem/emem_lst.