OpenApps

Parallel Search MCP server — tools & history

Parallel Search MCP server: observed open status, tool schemas, linked apps and version history.

Parallel Search

Endpoint: https://search.parallel.ai/mcp

Observed status: open. Checked: 2026-10-11T06:22:10+00:00.

Linked apps

Observed tools

  • web_fetch — Purpose: Fetch and extract relevant content from specific web URLs. Use only when web_search excerpts are insufficient for the task at hand. Ideal Use Cases: - The user asked about a specific URL or page - You need exact wording or quotes that excerpts may have truncated - You need full-page analysis (long article, document, or page structure) - web_search excerpts are conflicting or clearly insufficient to answer For multiple independent extraction objectives, make separate web_fetch calls concurrently. Put related URLs that share one objective in a single call.
  • web_search — Purpose: Perform web searches and return LLM-friendly results, including excerpts that are usually sufficient to answer directly without a follow-up fetch. Ideal Use Cases: - Answering questions that require fresh or current information - Research, comparison, documentation, and troubleshooting questions - Broad tasks where multiple `search_queries` can be issued in a single call For multiple independent objectives, make one web_search call per objective concurrently. Put related query variations for the same objective in a single call's search_queries list.

Data as of 2026-10-11T06:22:10+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections