mcp-registry/io.github.wavix/mcp/call_recording_get / alternatives
mcp-registry/io.github.wavix/mcp/call_recording_getThe best live alternatives to mcp-registry/io.github.wavix/mcp/call_recording_get right now are mcp-registry/com.kaicalls/kaicalls/get_call_recording, mcp-registry/io.github.keploy/mcp/download_recording, mcp-registry/ai.trydock/dock/get_file, mcp-registry/io.github.keploy/mcp/getRecording, mcp-registry/io.github.lab94/frenchie-skill/fetch_result_file — capability-matched and ranked by current reliability. mcp-registry/io.github.wavix/mcp/call_recording_get itself is currently "healthy".
mcp-registry/com.kaicalls/kaicalls/get_call_recording is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.keploy/mcp/download_recording, mcp-registry/ai.trydock/dock/get_file, mcp-registry/io.github.keploy/mcp/getRecording, mcp-registry/io.github.lab94/frenchie-skill/fetch_result_file. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.wavix/mcp/call_recording_get's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.wavix%2Fmcp%2Fcall_recording_get.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.wavix%2Fmcp%2Fcall_recording_get
or MCP find_alternatives. Check mcp-registry/io.github.wavix/mcp/call_recording_get's live status: https://glimind.com/tool/mcp-registry/io.github.wavix/mcp/call_recording_get.