mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance / alternatives

Live alternatives to mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance

The best live alternatives to mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance right now are mcp-registry/io.github.pipeworx-io/google_search_console/gsc_search_analytics, mcp-registry/com.zobrx/zobrx/get_seo_queries, mcp-registry/io.corpusiq/multi-source-mcp/search_console_connector, mcp-registry/app.toolsnap/toolsnap-mcp/keyword_research, mcp-registry/io.github.vee3io/vee3/seo.keyword_metrics — capability-matched and ranked by current reliability. mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/google_search_console/gsc_search_analytics	io.github.pipeworx-io/google_search_console	live status →
mcp-registry/com.zobrx/zobrx/get_seo_queries	com.zobrx/zobrx	live status →
mcp-registry/io.corpusiq/multi-source-mcp/search_console_connector	io.corpusiq/multi-source-mcp	live status →
mcp-registry/app.toolsnap/toolsnap-mcp/keyword_research	app.toolsnap/toolsnap-mcp	live status →
mcp-registry/io.github.vee3io/vee3/seo.keyword_metrics	io.github.Vee3io/vee3	live status →
mcp-registry/com.metricspot/seo-mcp/get_organic_traffic	com.metricspot/seo-mcp	live status →
mcp-registry/com.pangolinfo/amazon-mcp/keyword_trends	com.pangolinfo/amazon-mcp	live status →
mcp-registry/io.github.pipeworx-io/seo-keywords/seo_keyword_overview	io.github.pipeworx-io/seo-keywords	live status →
mcp-registry/io.github.pipeworx-io/semrush/domain_organic_keywords	io.github.pipeworx-io/semrush	live status →
mcp-registry/io.github.vee3io/vee3/google-search.url_traffic_insights	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.vee3io/vee3/google-search.keyword_traffic_insights	io.github.Vee3io/vee3	live status →
mcp-registry/io.github.pipeworx-io/seo-keywords-ads/seo_keyword_google_ads_volume	io.github.pipeworx-io/seo-keywords-ads	live status →

FAQ

What is the best alternative to mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance?

mcp-registry/io.github.pipeworx-io/google_search_console/gsc_search_analytics is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.zobrx/zobrx/get_seo_queries, mcp-registry/io.corpusiq/multi-source-mcp/search_console_connector, mcp-registry/app.toolsnap/toolsnap-mcp/keyword_research, mcp-registry/io.github.vee3io/vee3/seo.keyword_metrics. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance down right now?

mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.toshihiroshishido%2Frevenuescope-mcp%2Fget_keyword_performance.

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.toshihiroshishido%2Frevenuescope-mcp%2Fget_keyword_performance or MCP find_alternatives. Check mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance's live status: https://glimind.com/tool/mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_keyword_performance.