mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph / alternatives

Live alternatives to mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph

The best live alternatives to mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph right now are mcp-registry/io.github.pipeworx-io/api-football/scan_dependency, mcp-registry/io.github.pipeworx-io/altos/scan_dependency, mcp-registry/io.github.pipeworx-io/agify/scan_dependency, mcp-registry/io.github.pipeworx-io/anapioficeandfire/scan_dependency, mcp-registry/io.github.pipeworx-io/airnow/scan_dependency — capability-matched and ranked by current reliability. mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/api-football/scan_dependency	io.github.pipeworx-io/api-football	live status →
mcp-registry/io.github.pipeworx-io/altos/scan_dependency	io.github.pipeworx-io/altos	live status →
mcp-registry/io.github.pipeworx-io/agify/scan_dependency	io.github.pipeworx-io/agify	live status →
mcp-registry/io.github.pipeworx-io/anapioficeandfire/scan_dependency	io.github.pipeworx-io/anapioficeandfire	live status →
mcp-registry/io.github.pipeworx-io/airnow/scan_dependency	io.github.pipeworx-io/airnow	live status →
mcp-registry/io.github.pipeworx-io/fmi/scan_dependency	io.github.pipeworx-io/fmi	live status →
mcp-registry/io.github.pipeworx-io/foodish/scan_dependency	io.github.pipeworx-io/foodish	live status →
mcp-registry/io.github.pipeworx-io/stat-gl/scan_dependency	io.github.pipeworx-io/stat-gl	live status →
mcp-registry/io.github.pipeworx-io/data-cityofnewyork/scan_dependency	io.github.pipeworx-io/data-cityofnewyork	live status →
mcp-registry/io.github.pipeworx-io/data-connecticut/scan_dependency	io.github.pipeworx-io/data-connecticut	live status →
mcp-registry/io.github.pipeworx-io/chargebee/scan_dependency	io.github.pipeworx-io/chargebee	live status →
mcp-registry/io.github.pipeworx-io/cdc/scan_dependency	io.github.pipeworx-io/cdc	live status →

FAQ

What is the best alternative to mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph?

mcp-registry/io.github.pipeworx-io/api-football/scan_dependency is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/altos/scan_dependency, mcp-registry/io.github.pipeworx-io/agify/scan_dependency, mcp-registry/io.github.pipeworx-io/anapioficeandfire/scan_dependency, mcp-registry/io.github.pipeworx-io/airnow/scan_dependency. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph down right now?

mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.jonnyton%2Fworkflow-universe-server%2Frun_graph.

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.jonnyton%2Fworkflow-universe-server%2Frun_graph or MCP find_alternatives. Check mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph's live status: https://glimind.com/tool/mcp-registry/io.github.jonnyton/workflow-universe-server/run_graph.