mcp-registry/io.github.keploy/mcp/invoke_tool / alternatives

Live alternatives to mcp-registry/io.github.keploy/mcp/invoke_tool

The best live alternatives to mcp-registry/io.github.keploy/mcp/invoke_tool right now are mcp-registry/io.favcrm/favcrm/execute_tool, mcp-registry/com.apideck/mcp/execute_tool, mcp-registry/com.nicheangle/niche/niche_whoami, mcp-registry/io.github.mcp-dir/olist-mcp/search_tools, mcp-registry/io.github.mcp-dir/cplug-mcp/search_tools — capability-matched and ranked by current reliability. mcp-registry/io.github.keploy/mcp/invoke_tool itself is currently "healthy".

alternativeserver
mcp-registry/io.favcrm/favcrm/execute_toolio.favcrm/favcrmlive status →
mcp-registry/com.apideck/mcp/execute_toolcom.apideck/mcplive status →
mcp-registry/com.nicheangle/niche/niche_whoamicom.nicheangle/nichelive status →
mcp-registry/io.github.mcp-dir/olist-mcp/search_toolsio.github.mcp-dir/olist-mcplive status →
mcp-registry/io.github.mcp-dir/cplug-mcp/search_toolsio.github.mcp-dir/cplug-mcplive status →
mcp-registry/io.github.mcp-dir/asaas-mcp/search_toolsio.github.mcp-dir/asaas-mcplive status →
mcp-registry/io.github.ninihen1/flowstudio-mcp/tool_searchio.github.ninihen1/flowstudio-mcplive status →
mcp-registry/com.drillable/gateway/callcom.drillable/gatewaylive status →
mcp-registry/io.github.codex-curator/studiomcphub/get_tool_schemaio.github.codex-curator/studiomcphublive status →
mcp-registry/ai.com.mcp/contabo/tool_searchai.com.mcp/contabolive status →
mcp-registry/com.wingmanprotocol.agent/gateway/discover_toolscom.wingmanprotocol.agent/gatewaylive status →
mcp-registry/com.wingmanprotocol.agent/gateway/get_tool_schemacom.wingmanprotocol.agent/gatewaylive status →

FAQ

What is the best alternative to mcp-registry/io.github.keploy/mcp/invoke_tool?

mcp-registry/io.favcrm/favcrm/execute_tool is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.apideck/mcp/execute_tool, mcp-registry/com.nicheangle/niche/niche_whoami, mcp-registry/io.github.mcp-dir/olist-mcp/search_tools, mcp-registry/io.github.mcp-dir/cplug-mcp/search_tools. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.keploy/mcp/invoke_tool down right now?

mcp-registry/io.github.keploy/mcp/invoke_tool's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.keploy%2Fmcp%2Finvoke_tool.

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.keploy%2Fmcp%2Finvoke_tool or MCP find_alternatives. Check mcp-registry/io.github.keploy/mcp/invoke_tool's live status: https://glimind.com/tool/mcp-registry/io.github.keploy/mcp/invoke_tool.