mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast / alternatives

Live alternatives to mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast

The best live alternatives to mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast right now are mcp-registry/com.wingmanprotocol.agent/gateway/rate_limit, mcp-registry/com.claribi/mcp-server/run_forecast, mcp-registry/io.satoshiapi/mcp/get_fees_forecast, mcp-registry/com.claribi/mcp-server/create_forecast, mcp-registry/com.adbutler/mcp-server/get_placement_forecast — capability-matched and ranked by current reliability. mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast itself is currently "healthy".

alternativeserver
mcp-registry/com.wingmanprotocol.agent/gateway/rate_limitcom.wingmanprotocol.agent/gatewaylive status →
mcp-registry/com.claribi/mcp-server/run_forecastcom.claribi/mcp-serverlive status →
mcp-registry/io.satoshiapi/mcp/get_fees_forecastio.satoshiapi/mcplive status →
mcp-registry/com.claribi/mcp-server/create_forecastcom.claribi/mcp-serverlive status →
mcp-registry/com.adbutler/mcp-server/get_placement_forecastcom.adbutler/mcp-serverlive status →
pulsemcp/adbutler/get_placement_forecastAdButlerlive status →
pulsemcp/adbutler/get_display_forecastAdButlerlive status →
mcp-registry/com.adbutler/mcp-server/get_display_forecastcom.adbutler/mcp-serverlive status →
mcp-registry/com.claribi/mcp-server/get_forecast_runcom.claribi/mcp-serverlive status →
mcp-registry/com.claribi/mcp-server/get_forecastcom.claribi/mcp-serverlive status →
mcp-registry/io.github.helphub369/utility-matrix/rate-limit-utilization-calculatorio.github.helphub369/utility-matrixlive status →
mcp-registry/io.github.pipeworx-io/pirate-weather/forecastio.github.pipeworx-io/pirate-weatherlive status →

FAQ

What is the best alternative to mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast?

mcp-registry/com.wingmanprotocol.agent/gateway/rate_limit is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.claribi/mcp-server/run_forecast, mcp-registry/io.satoshiapi/mcp/get_fees_forecast, mcp-registry/com.claribi/mcp-server/create_forecast, mcp-registry/com.adbutler/mcp-server/get_placement_forecast. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast down right now?

mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.lazymac2x%2Fai-rate-limit-tracker%2Fget_forecast.

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.lazymac2x%2Fai-rate-limit-tracker%2Fget_forecast or MCP find_alternatives. Check mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast's live status: https://glimind.com/tool/mcp-registry/io.github.lazymac2x/ai-rate-limit-tracker/get_forecast.