mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs / alternatives
mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logsThe best live alternatives to mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs right now are mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions, mcp-registry/io.github.shree-git/sendit/get_workflow_run, mcp-registry/network.tenzro/tenzro/get_workflow, mcp-registry/org.memoryapi/cron/get_execution_history, mcp-registry/io.github.shree-git/sendit/list_workflows — capability-matched and ranked by current reliability. mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs itself is currently "healthy".
mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.shree-git/sendit/get_workflow_run, mcp-registry/network.tenzro/tenzro/get_workflow, mcp-registry/org.memoryapi/cron/get_execution_history, mcp-registry/io.github.shree-git/sendit/list_workflows. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.ctrlabs%2Fctrl-mcp%2Fctrl_get_execution_logs.
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.ctrlabs%2Fctrl-mcp%2Fctrl_get_execution_logs
or MCP find_alternatives. Check mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs's live status: https://glimind.com/tool/mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs.