mcp-registry/io.github.wavix/mcp/call_control_get / alternatives

Live alternatives to mcp-registry/io.github.wavix/mcp/call_control_get

The best live alternatives to mcp-registry/io.github.wavix/mcp/call_control_get right now are mcp-registry/io.famulor/famulor-mcp/get_call, mcp-registry/com.kaicalls/kaicalls/check_call_status, mcp-registry/io.github.agentlinehq/agentline/get_call_details, mcp-registry/com.kaicalls/kaicalls/get_call_recording, mcp-registry/io.github.pipeworx-io/gong/gong_get_call — capability-matched and ranked by current reliability. mcp-registry/io.github.wavix/mcp/call_control_get itself is currently "healthy".

alternative	server
mcp-registry/io.famulor/famulor-mcp/get_call	io.famulor/famulor-mcp	live status →
mcp-registry/com.kaicalls/kaicalls/check_call_status	com.kaicalls/kaicalls	live status →
mcp-registry/io.github.agentlinehq/agentline/get_call_details	io.github.AgentLineHQ/agentline	live status →
mcp-registry/com.kaicalls/kaicalls/get_call_recording	com.kaicalls/kaicalls	live status →
mcp-registry/io.github.pipeworx-io/gong/gong_get_call	io.github.pipeworx-io/gong	live status →
mcp-registry/io.famulor/famulor-mcp/delete_call	io.famulor/famulor-mcp	live status →
mcp-registry/io.famulor/famulor-mcp/get_mid_call_tool	io.famulor/famulor-mcp	live status →
mcp-registry/io.github.saloprj/dialogbrain/calls_get_transcript	io.github.saloprj/dialogbrain	live status →
mcp-registry/io.github.kimjin8/call-for-me/get_call_status	io.github.kimjin8/call-for-me	live status →
mcp-registry/com.lobbyvoices/receptionist-toolkit/get_demo_call_number	com.lobbyvoices/receptionist-toolkit	live status →
mcp-registry/io.famulor/famulor-mcp/make_call	io.famulor/famulor-mcp	live status →
mcp-registry/com.kaicalls/kaicalls/get_transcript	com.kaicalls/kaicalls	live status →

FAQ

What is the best alternative to mcp-registry/io.github.wavix/mcp/call_control_get?

mcp-registry/io.famulor/famulor-mcp/get_call is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.kaicalls/kaicalls/check_call_status, mcp-registry/io.github.agentlinehq/agentline/get_call_details, mcp-registry/com.kaicalls/kaicalls/get_call_recording, mcp-registry/io.github.pipeworx-io/gong/gong_get_call. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.wavix/mcp/call_control_get down right now?

mcp-registry/io.github.wavix/mcp/call_control_get's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.wavix%2Fmcp%2Fcall_control_get.

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.wavix%2Fmcp%2Fcall_control_get or MCP find_alternatives. Check mcp-registry/io.github.wavix/mcp/call_control_get's live status: https://glimind.com/tool/mcp-registry/io.github.wavix/mcp/call_control_get.