Rival search mcp
Deterministic deep research via RivalSearchMCP. 9 tools: 5-engine web search (DuckDuckGo/Bing/Yahoo/Mojeek/Wikipedia), 9-platform social search (Reddit/HN/StackOverflow/Dev.to/Medium/ProductHunt/Bluesky/Lobste.rs/Lemmy), 5-source news (Google/Bing/Guardian/GDELT/DDG), 5 academic DBs (OpenAlex/CrossRef/arXiv/PubMed/EuropePMC), GitHub search, website mapping, content extraction with OCR, and research topic synthesis. No API keys required. Use when the user needs web research, competitive analysis, content discovery, or academic paper search.From its SKILL.md
npx -y skills add damionrashford/RivalSearchMCP --skill rival-search-mcpAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 1 command, including `uv run scripts/cli.py call-tool <tool_name> --flag value`.
SKILL.md
3.2 KB, 636 tokens by cl100k_base, as published. Nobody here has run it
RivalSearchMCP
You have access to 9 research tools via the CLI at scripts/cli.py. Run all commands with uv run scripts/cli.py.
Every tool returns deterministic, auditable output. There is no in-server LLM — you're the one doing the synthesis.
How to invoke tools
uv run scripts/cli.py call-tool <tool_name> --flag value
Available tools
web_search— concurrent search across DuckDuckGo, Bing, Yahoo, Mojeek, Wikipedia. Use for general web queries.social_search— Reddit, Hacker News, Stack Overflow, Dev.to, Medium, Product Hunt, Bluesky, Lobste.rs, Lemmy. Use for community discussions.news_aggregation— Google News, Bing News, The Guardian, GDELT, DuckDuckGo News. Use for current events. Accepts--time-range day|week|month|anytime.github_search— search public GitHub repos. Use for code, libraries, projects.map_website— crawl a site inresearch/docs/mapmode. Use to explore site structure or documentation.content_operations— one tool, six ops (retrieve,stream,analyze,extract,score,find_conflicts). Use to get full page content, rate source quality, or surface disagreements between sources.document_analysis— extract text from PDFs, Word docs, images (image OCR via EasyOCR). Use for document processing.research_topic— end-to-end research workflow for a topic, combining search, content retrieval, and analysis.scientific_research— OpenAlex, CrossRef, arXiv, PubMed, Europe PMC (papers) + Kaggle, HuggingFace, Dataverse, Zenodo (datasets).
When to chain tools
- Found a URL from search? →
content_operations --operation retrieve --url <url> - Want to assess source trust before using results? →
content_operations --operation score --urls '[…]' - Two sources seem to disagree? →
content_operations --operation find_conflicts --urls '[…]' - Found a PDF link? →
document_analysis --url <url> - Need to explore a website? →
map_website --url <url> --mode docs - Need a unified entity profile in one shot? →
research_topic --mode entity --topic "OpenAI"
Tool reference
For full flags, types, and defaults for each tool, read:
- resources/search.md — web_search, social_search, news_aggregation, github_search, map_website
- resources/content.md — content_operations, document_analysis
- resources/research.md — research_topic, scientific_research
Output
All tools return structured text to stdout. Errors go to stderr. Exit codes: 0 success, 1 tool error, 2 connection failed.
What ships with it: 4 files
31.4 KB alongside SKILL.md, 1 of them executable
resources/
- content.md3.3 KB
- research.md2.1 KB
- search.md4.5 KB
scripts/
- cli.pyruns21.5 KB
Gives 0 of the 12 instructions most mcp tooling skills give in 636 tokens
Counted across 780 of the 1,136 authors here whose files we hold, read 2026-09-06
- Use Zod for input validationin 34 of 780, across 21 files
- Use stdio for local clientsin 27 of 780, across 10 files
- Restart Claude Code after configurationin 26 of 780, across 23 files
- Verify MCP server connection before using toolsin 23 of 780, across 17 files
- Define input schemas for every toolin 20 of 780, across 11 files
- Use Streamable HTTP for remote clientsin 18 of 780, across 8 files
- Pin SDK version in package.jsonin 17 of 780, across 6 files
- Keep server logic independent of transportin 16 of 780, across 6 files
- Verify SDK methods against official documentationin 15 of 780, across 5 files
- Format evaluation results as an XML filein 15 of 780, across 12 files
- Test servers using the MCP Inspectorin 15 of 780, across 14 files
- Create ten complex and independent evaluation questionsin 14 of 780, across 11 files
Said here and by no other author read
- Run all commands with uv run scripts/cli.py
- Use web_search for general web queries
- Use social_search for community discussions
- Use news_aggregation for current events
- Use github_search for code and projects
- Use map_website to explore site structure
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.