mcp-stealth-browser

Overview Schema Source Related Servers Discussions Admin

stealth_search

Search the real-time web across DuckDuckGo and Google without API keys, using stealth proxy rotation to bypass blocks and return ranked citations with titles, URLs, and snippets.

Instructions

Search the real-time web across multiple engines (DuckDuckGo, Google) without requiring any API keys. Returns ranked citations with titles, URLs, and snippets.

Args: query: Search query terms. num_results: Number of results to return (default: 5, max: 15). session_id: Optional sticky proxy session ID.

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": "stealth_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`session_id`	No
`num_results`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description explains the tool's behavior: it searches the web and returns ranked citations. It does not explicitly mention side effects like proxy rotation or network activity, but the optional session_id parameter hints at proxy usage. No annotations are present, so the description carries the full burden and covers the primary behavior adequately.

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?

The description is concise and well-structured, with a clear opening sentence followed by a parameter list. No unnecessary information or redundancy.

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?

The description provides enough context for an agent to decide when to use this tool. It does not explicitly state that it is read-only or non-destructive, but the nature of a search implies that. An output schema is present, so return format is already defined. Overall, sufficient for correct usage.

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

Parameters5/5

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

All three parameters are described in the tool description: query (search terms), num_results (count with default and max), and session_id (optional sticky proxy session). Even though the schema has no per-parameter descriptions, the tool description fully covers them.

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

Purpose5/5

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

The description clearly states the tool performs a web search across multiple engines (DuckDuckGo, Google) and returns ranked citations with titles, URLs, and snippets. It explicitly distinguishes it from potential alternatives by mentioning no API keys required.

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

Usage Guidelines4/5

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

The description implies usage for general web search tasks, mentioning real-time results and multi-engine support. While it does not explicitly contrast with sibling tools (stealth_fetch, proxy_status, rotate_proxy), the purpose is distinct and the sibling names are self-explanatory.

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

Deploy Server