MCP Server for Stealth Web Search and Fetching
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| websearchA | Search the web using DuckDuckGo or Google. Returns a clean list of titles, URLs, and snippets. Excellent for researching general knowledge, news, and finding URLs. |
| webfetchA | Fetch and extract the main text content from any webpage. Fully executes JavaScript to load React/SPAs and aggressively strips images/media (including base64) to save context tokens. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: websearch discovers URLs and snippets via search engines, while webfetch extracts content from a specific webpage. There is no overlap or ambiguity about which tool to use.
Both names follow the same predictable pattern: a 'web' prefix combined with a clear action verb (search, fetch). The lowercase concatenated style is consistent across the entire toolset.
With only two tools, the surface feels minimal and borderline thin, even though each tool covers a necessary core capability. The count is reasonable for the narrow search-and-fetch purpose but sits at the low end of the expected range.
The tools form a natural search-then-fetch workflow with no dead end: websearch provides URLs, and webfetch retrieves page content. Minor gaps exist, such as no explicit pagination or advanced crawling tools, but the core domain is well covered.