mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario / alternatives

Live alternatives to mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario

The best live alternatives to mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario right now are mcp-registry/io.github.davidgringras/scrutica/scrutica_get_scenario, mcp-registry/com.phasefolio/phasefolio/get_scenario, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news — capability-matched and ranked by current reliability. mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario itself is currently "healthy".

alternative	server
mcp-registry/io.github.davidgringras/scrutica/scrutica_get_scenario	io.github.davidgringras/scrutica	live status →
mcp-registry/com.phasefolio/phasefolio/get_scenario	com.phasefolio/phasefolio	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk	io.github.SupplyMaven-SCR/supply-chain-intelligence	live status →
mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news	io.github.vinaybhosle/shippingrates-mcp-server	live status →
mcp-registry/io.github.fxmacrodata/fxmacrodata/quant_scenario_lab_task	io.github.fxmacrodata/fxmacrodata	live status →
mcp-registry/io.github.fxmacrodata/fxmacrodata/policy_scenario_modeler_task	io.github.fxmacrodata/fxmacrodata	live status →
mcp-registry/io.github.skalinin909/tradingcalc/workflow.run_scenario_planning	io.github.SKalinin909/tradingcalc	live status →
mcp-registry/com.queuesim/public/simulate_scenario	com.queuesim/public	live status →
mcp-registry/co.ainumbers/tools/compute_rwa_scenarios	co.ainumbers/tools	live status →
mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/scenario_what_if	io.github.sugukurukabe/japan-real-estate-intel-mcp	live status →
mcp-registry/com.scmodeling/public/run_simulation	com.scmodeling/public	live status →

FAQ

What is the best alternative to mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario?

mcp-registry/io.github.davidgringras/scrutica/scrutica_get_scenario is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.phasefolio/phasefolio/get_scenario, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_risk_score, mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_corridor_risk, mcp-registry/io.github.vinaybhosle/shippingrates-mcp-server/shippingrates_congestion_news. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario down right now?

mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.baneado98%2Ffreight-pulse%2Fsimulate_scenario.

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.baneado98%2Ffreight-pulse%2Fsimulate_scenario or MCP find_alternatives. Check mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario's live status: https://glimind.com/tool/mcp-registry/io.github.baneado98/freight-pulse/simulate_scenario.