mcp-registry/io.github.triumsebas/unlimited-mcp/run_command / alternatives
mcp-registry/io.github.triumsebas/unlimited-mcp/run_commandThe best live alternatives to mcp-registry/io.github.triumsebas/unlimited-mcp/run_command right now are mcp-registry/com.vandorla/workspace-tools/execute_command — capability-matched and ranked by current reliability. mcp-registry/io.github.triumsebas/unlimited-mcp/run_command itself is currently "unknown".
| alternative | server | |
|---|---|---|
| mcp-registry/com.vandorla/workspace-tools/execute_command | com.vandorla/workspace-tools | live status → |
mcp-registry/com.vandorla/workspace-tools/execute_command is the top capability-matched alternative that's live right now. Other options: see the list. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.triumsebas/unlimited-mcp/run_command's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.triumsebas%2Funlimited-mcp%2Frun_command.
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.triumsebas%2Funlimited-mcp%2Frun_command
or MCP find_alternatives. Check mcp-registry/io.github.triumsebas/unlimited-mcp/run_command's live status: https://glimind.com/tool/mcp-registry/io.github.triumsebas/unlimited-mcp/run_command.