mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions

The best live alternatives to mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions right now are mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs, mcp-registry/io.github.shree-git/sendit/list_workflows, mcp-registry/org.memoryapi/cron/get_execution_history, mcp-registry/io.github.farestrabs/agentnet/get_execution, mcp-registry/com.b2bware/mcp-server/list_flow_runs — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions itself is currently "healthy".

alternative	server
mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs	io.github.CTRLabs/ctrl-mcp	live status →
mcp-registry/io.github.shree-git/sendit/list_workflows	io.github.Shree-git/sendit	live status →
mcp-registry/org.memoryapi/cron/get_execution_history	org.memoryapi/cron	live status →
mcp-registry/io.github.farestrabs/agentnet/get_execution	io.github.farestrabs/agentnet	live status →
mcp-registry/com.b2bware/mcp-server/list_flow_runs	com.b2bware/mcp-server	live status →
mcp-registry/io.sentinelsignal/scoring/list_workflows	io.sentinelsignal/scoring	live status →
mcp-registry/ai.trydock/dock/get_recent_events	ai.trydock/dock	live status →
mcp-registry/io.github.shree-git/sendit/get_workflow_run	io.github.Shree-git/sendit	live status →
mcp-registry/ai.dreamlit/mcp/list_workflows	ai.dreamlit/mcp	live status →
mcp-registry/io.github.dotnova/context-layer/list_sessions	io.github.DotNova/context-layer	live status →
mcp-registry/ai.plith/plith/rigor_workflows	ai.plith/plith	live status →
mcp-registry/network.tenzro/tenzro/list_workflows_by_status	network.tenzro/tenzro	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions?

mcp-registry/io.github.ctrlabs/ctrl-mcp/ctrl_get_execution_logs is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.shree-git/sendit/list_workflows, mcp-registry/org.memoryapi/cron/get_execution_history, mcp-registry/io.github.farestrabs/agentnet/get_execution, mcp-registry/com.b2bware/mcp-server/list_flow_runs. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions down right now?

mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fn8n%2Fn8n_list_executions.

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.pipeworx-io%2Fn8n%2Fn8n_list_executions or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/n8n/n8n_list_executions.