mcp-registry/io.github.obscuritysrl/bun-uia/window.restore / alternatives

Live alternatives to mcp-registry/io.github.obscuritysrl/bun-uia/window.restore

The best live alternatives to mcp-registry/io.github.obscuritysrl/bun-uia/window.restore right now are mcp-registry/io.github.trycourier/courier/restore_list, mcp-registry/tools.growthkit/revenue-intelligence/restoreVersion, mcp-registry/cloud.theprotocol/registry/theprotocol_restoreBundle, mcp-registry/io.favcrm/favcrm/restore_promotion, mcp-registry/io.favcrm/favcrm/restore_knowledge_document — capability-matched and ranked by current reliability. mcp-registry/io.github.obscuritysrl/bun-uia/window.restore itself is currently "unknown".

alternative	server
mcp-registry/io.github.trycourier/courier/restore_list	io.github.trycourier/courier	live status →
mcp-registry/tools.growthkit/revenue-intelligence/restoreVersion	tools.growthkit/revenue-intelligence	live status →
mcp-registry/cloud.theprotocol/registry/theprotocol_restoreBundle	cloud.theprotocol/registry	live status →
mcp-registry/io.favcrm/favcrm/restore_promotion	io.favcrm/favcrm	live status →
mcp-registry/io.favcrm/favcrm/restore_knowledge_document	io.favcrm/favcrm	live status →
mcp-registry/io.github.foundrynet/forge-mcp/restore_automation	io.github.FoundryNet/forge-mcp	live status →
mcp-registry/io.favcrm/favcrm/restore_invoice	io.favcrm/favcrm	live status →
mcp-registry/io.favcrm/favcrm/restore_campaign	io.favcrm/favcrm	live status →
pulsemcp/100hires/hires_restore_company	100Hires	live status →
mcp-registry/com.100hires/100hires/hires_restore_company	com.100hires/100hires	live status →
mcp-registry/io.simplyprint/simplyprint/unarchive_print_job	io.simplyprint/simplyprint	live status →

FAQ

What is the best alternative to mcp-registry/io.github.obscuritysrl/bun-uia/window.restore?

mcp-registry/io.github.trycourier/courier/restore_list is the top capability-matched alternative that's live right now. Other options: mcp-registry/tools.growthkit/revenue-intelligence/restoreVersion, mcp-registry/cloud.theprotocol/registry/theprotocol_restoreBundle, mcp-registry/io.favcrm/favcrm/restore_promotion, mcp-registry/io.favcrm/favcrm/restore_knowledge_document. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.obscuritysrl/bun-uia/window.restore down right now?

mcp-registry/io.github.obscuritysrl/bun-uia/window.restore's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.obscuritysrl%2Fbun-uia%2Fwindow.restore.

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.obscuritysrl%2Fbun-uia%2Fwindow.restore or MCP find_alternatives. Check mcp-registry/io.github.obscuritysrl/bun-uia/window.restore's live status: https://glimind.com/tool/mcp-registry/io.github.obscuritysrl/bun-uia/window.restore.