feat(integrations): add free You.com search MCP

[mouse-value-add]

• A human has tested these changes.

---

HUMAN: Tested the full Stackable-HTTP path against the live keyless endpoint — initialize → tools/list → tools/call you-search — plus ran the catalog, schema, and index-sync test suites locally; all green. Details in How to Test.

Why

The catalog's current web-search MCP options (tavily, exa, firecrawl, kagi) all require API keys, so a fresh install has no working web search until the user signs up somewhere. The You.com MCP server exposes an anonymous free tier that works out of the box, which makes it a good zero-setup option alongside the keyed providers.

Summary

• New catalog entry youcom-search: You.com MCP over Streamable HTTP at the keyless free-tier endpoint (https://api.you.com/mcp?profile=free), no-auth connection option
• tests/test_catalogs.py: added youcom-search to the intentionally-public remote MCP ids
• tests/test_live_integration_smoke.py: opt-in live smoke test (RUN_YOUCOM_MCP_LIVE=1) exercising you-search through the same create_mcp_tools stack the Agent Canvas probe uses

Issue Number

Fixes #601

How to Test

npm run build:integrations
uv run --group test pytest tests/test_catalogs.py::test_remote_no_auth_mcp_entries_are_intentionally_public tests/test_catalog_schema.py tests/test_integration_catalog_in_sync.py -q
RUN_YOUCOM_MCP_LIVE=1 uv run --group test pytest tests/test_live_integration_smoke.py -k youcom -s

All three pass locally (106 passed incl. schema + index sync; live smoke passes with zero warnings).

Video/Screenshots

Tested the endpoint directly over Streamable HTTP (initialize → tools/list → you-search), no credentials:

tools/list  ->  ['you-search', 'you-discover']
tools/call you-search {"query": "OpenHands AI agent platform GitHub repository", "count": 5}
[OSS-5193] youcom: anonymous you-search -> 5 web results
1 passed, 6 deselected in 2.79s

Notes

• integrations/catalog-index.js was regenerated with npm run build:integrations, not hand-edited.
• The free-tier endpoint is anonymous and rate-limited; a keyed tier exists at https://api.you.com/mcp for higher limits but is intentionally not wired into this entry.

[mouse-value-add]

The "Validate PR description" check is failing on linked-issue readiness: #601 was created today and doesn't yet carry the ready-for-dev label, so the gate blocks the PR by design. That's a maintainer-side call — I can't apply labels here as an outside contributor.

If the issue looks ready to you, applying ready-for-dev to #601 (or folding this into an existing ready issue if you'd rather track it elsewhere) will let the required checks run. Everything else on the PR is self-contained: the catalog entry, regenerated catalog-index.js, and the tests all pass locally per the description.

[all-hands-bot]

👋 This PR needs a couple of things fixed before OpenHands can review it:

• the PR description's HUMAN: section needs at least 20 characters describing what you tested, not just the template placeholder

Push an update once this is addressed and this check re-runs automatically.

This is an automated check - no AI was used to generate this comment.

[all-hands-bot]

🚦 CI is currently failing on this PR's latest commit.

Please fix the failing checks before OpenHands reviews it - this is re-checked automatically once you push a new commit. (A maintainer can also request @all-hands-bot as a reviewer to have it reviewed regardless of CI status.)

This is an automated check - no AI was used to generate this comment.