Rivalsearchmcp

Created By
damionrashford9 months ago
Advanced MCP server for comprehensive web research, content discovery, and trends analysis. Features multi-engine search, intelligent content extraction, website traversal, and real-time data streaming.
Overview

What is RivalSearchMCP?

RivalSearchMCP is an advanced MCP server designed for comprehensive web research, content discovery, and trends analysis, offering tools for multi-engine search and intelligent content extraction.

How to use RivalSearchMCP?

To get started, connect to the live server by adding the provided configuration to your MCP client, such as Cursor, Claude Desktop, or VS Code. Follow the specific instructions for each platform to integrate the server.

Key features of RivalSearchMCP?

  • Multi-engine search capabilities with anti-detection measures.
  • Intelligent content extraction and website traversal.
  • Real-time data streaming and progress tracking for research workflows.
  • Comprehensive export options for trends data in various formats (CSV, JSON, SQL).

Use cases of RivalSearchMCP?

  1. Conducting in-depth web research for academic or market analysis.
  2. Analyzing trends data for business insights and decision-making.
  3. Extracting and processing content from multiple web sources efficiently.

FAQ from RivalSearchMCP?

  • Can RivalSearchMCP bypass web scraping protections?

Yes, it includes features like Cloudflare bypass for reliable scraping.

  • Is there documentation available for using RivalSearchMCP?

Yes, comprehensive documentation is available here.

  • How can I contribute to the project?

Contributions are welcome as it is an open-source project maintained by the community.

Server Config

{
  "mcpServers": {
    "RivalSearchMCP": {
      "url": "https://RivalSearchMCP.fastmcp.app/mcp"
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
damionrashford
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago