Rush Radar: Niche Finder & Trend Radar

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.0Updated Oct 25, 2026

Check product ideas against live demand, plus a daily brief of new launches and rising tools.

The publisher's own server: Rush SR Lap Analyzer

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

A remote Apify-hosted MCP server that checks product ideas against live demand and delivers a daily brief of new launches and rising tools.

What you can do
Check a product idea against live demand signals and see how much interest it attracts. Get a daily brief of newly launched products and tools that are gaining traction. Use the results to judge whether an idea is worth pursuing before building it.
When to use it
Useful when you are weighing a product or niche idea and want current market signals rather than guesswork, or when you want a recurring digest of new launches and rising tools.
Requirements
A remote MCP endpoint at mcp.apify.com, reachable over the network. An Apify account with an API token supplied as a Bearer token in the Authorization header; OAuth is also declared as required.
Before you install
The Authorization header carries your Apify API token, so treat it as a secret. Runs are billed per event to your Apify account, so usage costs money. Requests and queries go to Apify's hosted service.

Installation

In SourceWeft

  1. Open Rush Radar: Niche Finder & Trend Radar in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Nero-Engine%2Frush-radar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rush-radar-niche-finder-trend-radar": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/rush-radar"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 24, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Rush integrations