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

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

The best live alternatives to mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_page_trend right now are mcp-registry/io.github.pipeworx-io/linkedin_ads/recent_changes, mcp-registry/io.github.pipeworx-io/lobsters/recent_changes, mcp-registry/io.github.pipeworx-io/lens-org/recent_changes, mcp-registry/io.github.pipeworx-io/market-spread/recent_changes, mcp-registry/io.github.pipeworx-io/mercury-number/recent_changes — capability-matched and ranked by current reliability. mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_page_trend itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/linkedin_ads/recent_changes	io.github.pipeworx-io/linkedin_ads	live status →
mcp-registry/io.github.pipeworx-io/lobsters/recent_changes	io.github.pipeworx-io/lobsters	live status →
mcp-registry/io.github.pipeworx-io/lens-org/recent_changes	io.github.pipeworx-io/lens-org	live status →
mcp-registry/io.github.pipeworx-io/market-spread/recent_changes	io.github.pipeworx-io/market-spread	live status →
mcp-registry/io.github.pipeworx-io/mercury-number/recent_changes	io.github.pipeworx-io/mercury-number	live status →
mcp-registry/io.github.pipeworx-io/makstat-mk/recent_changes	io.github.pipeworx-io/makstat-mk	live status →
mcp-registry/io.github.pipeworx-io/mailchimp/recent_changes	io.github.pipeworx-io/mailchimp	live status →
mcp-registry/io.github.pipeworx-io/malwarebazaar/recent_changes	io.github.pipeworx-io/malwarebazaar	live status →
mcp-registry/io.github.pipeworx-io/lorem/recent_changes	io.github.pipeworx-io/lorem	live status →
mcp-registry/io.github.pipeworx-io/lyrics-ovh/recent_changes	io.github.pipeworx-io/lyrics-ovh	live status →
mcp-registry/io.github.pipeworx-io/kalshi/recent_changes	io.github.pipeworx-io/kalshi	live status →
mcp-registry/io.github.pipeworx-io/jira/recent_changes	io.github.pipeworx-io/jira	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/linkedin_ads/recent_changes is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/lobsters/recent_changes, mcp-registry/io.github.pipeworx-io/lens-org/recent_changes, mcp-registry/io.github.pipeworx-io/market-spread/recent_changes, mcp-registry/io.github.pipeworx-io/mercury-number/recent_changes. Glimind ranks alternatives by semantic similarity and live health.

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

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

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