Add Parallel Search MCP to the integration catalog

[georgeatparallel]

Desired Behavior

I'm George from Parallel. I'd like to make Parallel Search MCP available in the shared integration catalog so OpenHands users can add web search and page fetching through the normal MCP settings, without entering an API key.

PR #528 implements this catalog addition. It uses the existing no-auth Streamable HTTP connection at https://search.parallel.ai/mcp. Search queries and fetched URLs go to Parallel's hosted service. Anonymous access is free for light use and rate-limited.

The entry is opt-in and preserves existing providers, search defaults and saved server settings. Availability in released clients depends on the catalog release and the consumer updating its package.

Acceptance Criteria

• The shared catalog includes parallel-search with the documented no-auth Streamable HTTP endpoint.
• The generated JavaScript index and packaged Python catalog expose the same entry.
• OpenHands can install the entry through its existing MCP settings without requesting a credential or replacing a saved server.
• The search and page-fetch tools return useful results with source links, and invalid arguments surface as errors.
• Existing integrations and default search routing keep their current behavior.

Validation

The existing PR has recorded catalog, packaging and consumer test results, plus an anonymous search/fetch smoke test. The PR describes the commands and limits. The hosted UI was not exercised.

Would you review the catalog addition in #528?

[github-actions]

⚠️ Not yet ready-for-dev

This issue does not yet meet the readiness criteria, so the
ready-for-dev label has not been applied (or has been removed).
The criteria are type-specific:

Bug reports (bug label):

• The ### Actual Behavior section must describe reproducible steps
  and include a command such as uv run pytest, pytest, python,
  pip, npm run, or node.
• An ### Acceptance Criteria section with at least one checklist item (- [ ] ...).

Enhancements (enhancement label):

• A ### Desired Behavior section.
• An ### Acceptance Criteria section with at least one checklist item.

What is missing:

• The issue has neither the bug nor enhancement label, so its readiness criteria cannot be evaluated. Add the appropriate label.

Edit the issue to address the gaps and the ready-for-dev label will be
applied automatically.

This is an automated readiness check posted by a workflow.