Web Search vs Agent Search MCP

A side-by-side look at the Web Search and Agent Search MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Web Search logoWeb SearchSearch & Data Extraction · Remote HTTP/SSEWeb search for AI agents — one tool across 6 engines, routed to the cheapest + cached.36FairAuth: not declaredAgent Search MCP logoAgent Search MCPSearch & Data Extraction · Local subprocess (stdio)Free multi-engine MCP search server — 8 free engines (DDG, Sogou, Bing, Baidu, Wikipedia, Startpage, Yandex, Mojeek), waterfall progressive search, multi-source verification, content enrichment, news search, language auto-detection, CLI. Zero API keys needed. npx agent-search-mcp67GreatAuth: no auth required

Verdict: choose Web Search for search & data extraction work over a hosted endpoint; choose Agent Search MCP for search & data extraction as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Web Search logoChoose Web Search when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: GROUNDROUTE_API_KEY.
Explore Web Search

Agent Search MCP logoChoose Agent Search MCP when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like free_search, free_search_advanced, free_extract.
Explore Agent Search MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecWeb Search logoWeb SearchAgent Search MCP logoAgent Search MCP
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal36/100 · Fair67/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsGROUNDROUTE_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1112
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed7

Tools & capabilities

Web Search tools

No tool names declared yet. Check the project README from the listing page.

Agent Search MCP tools 7

  • free_searchQuick public-web search for current facts and discovery. Use free_search_advanced for verification or domain filters. Use free_extract for one selected URL. Returns compact multi-source evidence with confidence, relevance, source_count, stop_reason, evidence_budget, and partialFailures. Provider families are counted once even when several adapters use the same upstream. Optional API providers run only when credentials and policy allow. @readOnly true @idempotent true — makes outbound HTTP requests to configured search engines. Injection detection and SSRF protection active.
  • free_search_advancedVerification-oriented search with domain filters and waterfall fallback. Use for claim checking, Chinese-source search, or publisher restrictions. Start with free_search for quick discovery. The response exposes source_count, stop_reason, evidence_budget, and partialFailures. @readOnly true @idempotent true — runs waterfall progressive search across policy-allowed engines. Makes outbound HTTP requests to search engines and optionally to Jina Reader for content enrichment.
  • free_extractExtract one selected URL into clean Markdown. Use after search when snippets are insufficient, or for a URL supplied by the user. It fetches one page; it does not search or bulk-extract URLs. Behavior: Makes an outbound HTTP request to Jina Reader (r.jina.ai) which fetches and converts the page to markdown. Has SSRF protection: blocks private IPs, localhost, and metadata endpoints. 10s request timeout — pages exceeding this will fail with a timeout error. HTTP errors (4xx, 5xx) are returned as structured error responses.
  • fetch_github_readmeFetch README content from a GitHub repository. Best for: Getting project documentation quickly. Not recommended for: Non-GitHub URLs — use free_extract instead. @readOnly true @idempotent true — makes outbound HTTP requests to raw.githubusercontent.com.
  • fetch_csdn_articleFetch content from a CSDN blog article. Best for: Chinese developer blog content on CSDN. Not recommended for: Other Chinese sites — use free_extract instead. @readOnly true @idempotent true — makes outbound HTTP requests to the CSDN article URL.
  • fetch_juejin_articleFetch content from a Juejin article. Best for: Chinese developer articles on Juejin. Not recommended for: Non-Juejin content — use free_extract instead. @readOnly true @idempotent true — makes outbound HTTP requests to juejin.cn API.
  • search_with_synthesisOpt-in deep search with waterfall verification and content enrichment. Returns structured results plus a prompt_hint; it does not call an external LLM. Use when multi-source evidence needs a synthesis handoff. free_search is the default for discovery; this path uses more tokens and network time. @readOnly true @idempotent true — runs waterfall search across free+paid engines with content enrichment.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Web Search

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "web-search": {
      "url": "https://api.groundroute.ai/mcp"
    }
  }
}

Agent Search MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "lennney-agent-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agent-search-mcp"
      ]
    }
  }
}

Frequently asked questions

Web Search is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Agent Search MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Web Search for search & data extraction work and Agent Search MCP for search & data extraction.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Web Search has no declared pricing — check the project's own site. Agent Search MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add web-search and lennney-agent-search-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Web Search has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Agent Search MCP has 67/100 (Great) with 4 views, 0 installs and 112 GitHub stars.