mcp-registry/house.bim/bimhouse/set_forkable / alternatives

Live alternatives to mcp-registry/house.bim/bimhouse/set_forkable

The best live alternatives to mcp-registry/house.bim/bimhouse/set_forkable right now are mcp-registry/cloud.theprotocol/registry/theprotocol_forkBundle, mcp-registry/io.github.yukihamada/tokkyo-maru/tokkyo_check, mcp-registry/house.device/device-house/parts_remove, mcp-registry/ai.namewhisper/ens-tools/manage_fuses, mcp-registry/io.github.yukihamada/tokkyo-maru/tokkyo_draft — capability-matched and ranked by current reliability. mcp-registry/house.bim/bimhouse/set_forkable itself is currently "healthy".

alternative	server
mcp-registry/cloud.theprotocol/registry/theprotocol_forkBundle	cloud.theprotocol/registry	live status →
mcp-registry/io.github.yukihamada/tokkyo-maru/tokkyo_check	io.github.yukihamada/tokkyo-maru	live status →
mcp-registry/house.device/device-house/parts_remove	house.device/device-house	live status →
mcp-registry/ai.namewhisper/ens-tools/manage_fuses	ai.namewhisper/ens-tools	live status →
mcp-registry/io.github.yukihamada/tokkyo-maru/tokkyo_draft	io.github.yukihamada/tokkyo-maru	live status →
mcp-registry/io.github.pipeworx-io/alchemy-eth/nft_owners	io.github.pipeworx-io/alchemy-eth	live status →
mcp-registry/io.github.mirabello-consultancy/mcp-server/forced_heirship_risk	io.github.mirabello-consultancy/mcp-server	live status →
mcp-registry/io.stablebaseline/sb/setResourcePermissionOverride	io.stablebaseline/sb	live status →
mcp-registry/ai.trydock/dock/revoke_file_share	ai.trydock/dock	live status →
mcp-registry/com.wingmanprotocol.agent/gateway/share_memory	com.wingmanprotocol.agent/gateway	live status →
mcp-registry/com.quintadb/mcp/set_module_permission	com.quintadb/mcp	live status →
mcp-registry/ru.quintadb/mcp/set_module_permission	ru.quintadb/mcp	live status →

FAQ

What is the best alternative to mcp-registry/house.bim/bimhouse/set_forkable?

mcp-registry/cloud.theprotocol/registry/theprotocol_forkBundle is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.yukihamada/tokkyo-maru/tokkyo_check, mcp-registry/house.device/device-house/parts_remove, mcp-registry/ai.namewhisper/ens-tools/manage_fuses, mcp-registry/io.github.yukihamada/tokkyo-maru/tokkyo_draft. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/house.bim/bimhouse/set_forkable down right now?

mcp-registry/house.bim/bimhouse/set_forkable's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fhouse.bim%2Fbimhouse%2Fset_forkable.

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%2Fhouse.bim%2Fbimhouse%2Fset_forkable or MCP find_alternatives. Check mcp-registry/house.bim/bimhouse/set_forkable's live status: https://glimind.com/tool/mcp-registry/house.bim/bimhouse/set_forkable.