mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool / alternatives

Live alternatives to mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool

The best live alternatives to mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool right now are mcp-registry/io.github.javierfajardo85-rgb/aiaam/get_tool, mcp-registry/io.github.wavix/mcp/call_control_get, mcp-registry/com.kaicalls/kaicalls/check_call_status, mcp-registry/ai.tunnelmind/scry/scry_tool, mcp-registry/io.github.alisammour/storyflo-mcp/get_mcp_usage_self — capability-matched and ranked by current reliability. mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool itself is currently "healthy".

alternative	server
mcp-registry/io.github.javierfajardo85-rgb/aiaam/get_tool	io.github.javierfajardo85-rgb/aiaam	live status →
mcp-registry/io.github.wavix/mcp/call_control_get	io.github.Wavix/mcp	live status →
mcp-registry/com.kaicalls/kaicalls/check_call_status	com.kaicalls/kaicalls	live status →
mcp-registry/ai.tunnelmind/scry/scry_tool	ai.tunnelmind/scry	live status →
mcp-registry/io.github.alisammour/storyflo-mcp/get_mcp_usage_self	io.github.Alisammour/storyflo-mcp	live status →
mcp-registry/io.github.szara7678/openakashic/debug_tool_trace	io.github.szara7678/openakashic	live status →
mcp-registry/com.wingmanprotocol.agent/gateway/get_tool_schema	com.wingmanprotocol.agent/gateway	live status →
mcp-registry/com.nicheangle/niche/niche_whoami	com.nicheangle/niche	live status →
mcp-registry/io.github.mcp-dir/olist-mcp/search_tools	io.github.mcp-dir/olist-mcp	live status →
mcp-registry/io.github.mcp-dir/cplug-mcp/search_tools	io.github.mcp-dir/cplug-mcp	live status →
mcp-registry/io.github.mcp-dir/asaas-mcp/search_tools	io.github.mcp-dir/asaas-mcp	live status →
mcp-registry/io.github.jonathanpchapman/inferventis/platform_tool_finder	io.github.jonathanpchapman/inferventis	live status →

FAQ

What is the best alternative to mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool?

mcp-registry/io.github.javierfajardo85-rgb/aiaam/get_tool is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.wavix/mcp/call_control_get, mcp-registry/com.kaicalls/kaicalls/check_call_status, mcp-registry/ai.tunnelmind/scry/scry_tool, mcp-registry/io.github.alisammour/storyflo-mcp/get_mcp_usage_self. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool down right now?

mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.famulor%2Ffamulor-mcp%2Fget_mid_call_tool.

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.famulor%2Ffamulor-mcp%2Fget_mid_call_tool or MCP find_alternatives. Check mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool's live status: https://glimind.com/tool/mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool.