Target Repository URL
https://github.com/damionrashford/RivalSearchMCP
You.com API(s)
search
Why this repo was selected
RivalSearchMCP is an active, under-200-star MCP server with search at the center of the product. It already has a clear engine-oriented search architecture, recent commits, and a solid test suite. A You.com provider fits naturally as an optional additional engine without changing the default behavior.
Candidate evaluation
- damionrashford/RivalSearchMCP: best fit today; 117 stars, active, strong search abstraction, good test coverage, clean optional integration path
- lianwusuoai/ai-search-mcp: active and under 200 stars, but the search surface is model-driven and less directly suited to a thin You.com API adapter
- adenot/mcp-google-search: small and active, but narrower and more credential-centric; the change would be straightforward but less aligned with the repo's current multi-source research model
Proposed integration type
Optional Search API provider / search engine adapter.
Planned env vars and setup
ENABLE_YOUCOM_SEARCH=true to opt into the You.com engine
YDC_API_KEY for authenticated access, if desired
- Existing providers remain unchanged when You.com is not configured
Expected usage example
ENABLE_YOUCOM_SEARCH=true YDC_API_KEY=... uv run python server.py
Validation plan
- Add unit coverage for provider registration and response mapping
- Run the repo's relevant checks:
pytest and any targeted provider/search tests available in the environment
- Confirm default search behavior stays unchanged when You.com is not selected
Fallback / error behavior
- Missing
YDC_API_KEY keeps the provider optional; the adapter can still use the keyless path
- HTTP failures surface a clear provider error and do not block the other engines
- Existing engines continue to run and aggregate results as before
Links
Implementation branch: https://github.com/mouse-value-add/RivalSearchMCP/tree/feat/youcom-search-integration
OSS PR: damionrashford/RivalSearchMCP#51
Status
status:pr-opened
Validation
python3 -m py_compile on the touched Python files
uv run pytest tests/tools/test_youcom_search.py -q
uv run pytest tests/tools/test_web_search.py -q
uv run ruff check on the touched Python files
Target Repository URL
https://github.com/damionrashford/RivalSearchMCP
You.com API(s)
search
Why this repo was selected
RivalSearchMCP is an active, under-200-star MCP server with search at the center of the product. It already has a clear engine-oriented search architecture, recent commits, and a solid test suite. A You.com provider fits naturally as an optional additional engine without changing the default behavior.
Candidate evaluation
Proposed integration type
Optional Search API provider / search engine adapter.
Planned env vars and setup
ENABLE_YOUCOM_SEARCH=trueto opt into the You.com engineYDC_API_KEYfor authenticated access, if desiredExpected usage example
Validation plan
pytestand any targeted provider/search tests available in the environmentFallback / error behavior
YDC_API_KEYkeeps the provider optional; the adapter can still use the keyless pathLinks
Implementation branch: https://github.com/mouse-value-add/RivalSearchMCP/tree/feat/youcom-search-integration
OSS PR: damionrashford/RivalSearchMCP#51
Status
status:pr-openedValidation
python3 -m py_compileon the touched Python filesuv run pytest tests/tools/test_youcom_search.py -quv run pytest tests/tools/test_web_search.py -quv run ruff checkon the touched Python files