mcp-registry/io.github.coder-ka/procm-mcp/get-process-stdout / alternatives
mcp-registry/io.github.coder-ka/procm-mcp/get-process-stdoutThe best live alternatives to mcp-registry/io.github.coder-ka/procm-mcp/get-process-stdout right now are mcp-registry/dev.danielsuchan/eu261/get_price_history, mcp-registry/io.github.codex-curator/studiomcphub/get_asset, mcp-registry/io.simplyprint/simplyprint/get_slicer_settings_for_file, mcp-registry/io.famulor/famulor-mcp/get_call, mcp-registry/social.superpowers/social-superpowers/reddit-get-posts — capability-matched and ranked by current reliability. mcp-registry/io.github.coder-ka/procm-mcp/get-process-stdout itself is currently "unknown".
mcp-registry/dev.danielsuchan/eu261/get_price_history is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.codex-curator/studiomcphub/get_asset, mcp-registry/io.simplyprint/simplyprint/get_slicer_settings_for_file, mcp-registry/io.famulor/famulor-mcp/get_call, mcp-registry/social.superpowers/social-superpowers/reddit-get-posts. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.coder-ka/procm-mcp/get-process-stdout's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.coder-ka%2Fprocm-mcp%2Fget-process-stdout.
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.coder-ka%2Fprocm-mcp%2Fget-process-stdout
or MCP find_alternatives. Check mcp-registry/io.github.coder-ka/procm-mcp/get-process-stdout's live status: https://glimind.com/tool/mcp-registry/io.github.coder-ka/procm-mcp/get-process-stdout.