web-search-plus

Web Search Plus

Web Search Plus gives you two MCP tools. Both return sources, never answers. You read the sources and synthesize; the server does not generate truth claims.

• web_search — multi-provider search with automatic routing. Returns ranked results with URL, title, snippet, provider, and routing metadata.
• web_extract — fetches one or more URLs and returns bounded markdown (or HTML), with optional query-ranked spans for long pages.

When to prefer these over the built-in search

• The user wants to see which sources say something, or wants a quality/routing report.
• The query is provider-shaped: docs/API lookups, arXiv, CVE/security, GitHub/OSS discovery, local/shopping, news with a recency window.
• The user wants a specific provider or a specific locale.
• You need the full text of a page, not a snippet. Use web_extract.
• The user says "wsp", "web search plus", or names a provider.

For quick, one-line factual lookups the built-in search is fine. Do not run both for the same question unless the user asks to compare.

web_search

Required: query.

Useful parameters:

• provider — auto (default) or one of serper, brave, tavily, linkup, exa, firecrawl, parallel, you, searxng, keenable, serpbase, querit, donsetch, octen, tinyfish. Only providers with a configured key work; leave auto unless the user asks.
• count — results, default 5, max 20.
• freshness — day, week, month, year for recency.
• search_type — news for a news vertical.
• country / language — locale overrides.
• include_domains / exclude_domains — allow or deny lists.
• mode — research queries up to three providers concurrently, dedupes, and extracts the top sources. Slower and costs more; use for deep questions.
• quality_report — true to include routing class, provider scores, and authority signals. Useful when the user asks why a result ranked where it did.

Example:

{ "query": "Hermes Agent 0.21 release notes", "freshness": "month", "count": 5 }