MCP Server for Stealth Web Search and Fetching

Overview Schema Source Related Servers Discussions Admin

Web Search

websearch

Read-only

Search the web via DuckDuckGo or Google to return numbered results with titles, URLs, and snippets for quick research and source gathering.

Instructions

Search the web with DuckDuckGo or Google and return numbered results with titles, URLs and snippets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "websearch"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	The search query.
`engine`	No	'duckduckgo' (default), 'google', a search template name, or an inline JSON search template. Built-in engines fall back to DuckDuckGo when unavailable.	duckduckgo
`region`	No	Region-language code such as 'us-en' or 'de-de'. DuckDuckGo uses it as-is; Google maps it to country (gl) and language (hl). Default: engine default.
`block_media`	No	Block images, media and fonts at the network layer. Default: true.
`max_results`	No	Maximum results to return. Default: 10.
`safe_search`	No	Enable (true) or disable (false) safe search. Default: engine default.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv4.0.0Oct 19, 2026

changedInput schema / properties / block_media / description

Previous value: -"Block images, videos, and fonts entirely at the network layer. Default is true."New value: +"Block images, media and fonts at the network layer. Default: true."

changedInput schema / properties / engine / description

Previous value: -"Search engine to use. Can be 'duckduckgo' or 'google'. Default is 'duckduckgo'."New value: +"'duckduckgo' (default), 'google', a search template name, or an inline JSON search template. Built-in engines fall back to DuckDuckGo when unavailable."

changedInput schema / properties / max_results / description

Previous value: -"Maximum number of search results to return. Default is 10."New value: +"Maximum results to return. Default: 10."

changedInput schema / properties / query / description

Previous value: -"The search query string."New value: +"The search query."

changedInput schema / properties / region / description

Previous value: -"Region and language code to localize search results (e.g., 'us-en', 'uk-en', 'de-de'). For DuckDuckGo it maps directly. For Google, 'us' is country code and 'en' is language. Default is null (uses template default)."New value: +"Region-language code such as 'us-en' or 'de-de'. DuckDuckGo uses it as-is; Google maps it to country (gl) and language (hl). Default: engine default."

changedInput schema / properties / safe_search / description

Previous value: -"Enable safe search filtering. null = use template default. Applies to both DuckDuckGo and Google."New value: +"Enable (true) or disable (false) safe search. Default: engine default."

Changed8 schema fields changedv3.3.4Sep 21, 2026
- addedInput schema / properties / max_results / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / max_results / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / max_results / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / query / minLength
```
Added value: +1
```
- removedInput schema / properties / region / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / region / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedInput schema / properties / safe_search / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / safe_search / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
First observedv3.3.2Aug 3, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description usefully adds the output format (numbered results with titles, URLs, snippets), but says nothing about pagination, result limits, or rate behavior beyond what the schema's max_results covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence that front-loads the action and resource, with no wasted words. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a straightforward read-only search tool with no output schema, the description conveys the essential action and return format, and annotations plus a 100%-documented schema carry the rest. Only the search-vs-fetch routing is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the schema already documents all six parameters in detail (engine fallback, region mapping, block_media, safe_search). The description adds no parameter-specific meaning beyond that baseline, so a 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (the web), names the supported engines, and describes the return shape (numbered results with titles, URLs, snippets). It clearly differs from webfetch, though the differentiation is left implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus the sibling webfetch, nor any prerequisites or exclusions. The agent must infer the search-vs-fetch distinction on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

webfetchA
websearchB