MCP Web Search Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEADLESS | No | Run browser in headless mode (true/false) | |
| PROXY_LIST | No | Comma-separated list of proxies for anti-detection | |
| BING_API_KEY | No | API key for Bing Web Search | |
| SERPER_API_KEY | No | API key for Serper.dev search provider | |
| STEALTH_ENABLED | No | Enable stealth anti-detection (true/false) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchB | Search the web for a query. Returns a list of results with title, URL, and snippet. Use provider='auto' to try all available search engines. |
| fetch_urlC | Fetch and extract clean text content from a URL. Optimized for LLM consumption with metadata. |
| search_and_fetchA | Search the web and automatically fetch content from top results. Returns combined LLM-formatted output. |
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 3 tools
Each tool serves a clearly distinct purpose: web_search returns a list of results, fetch_url extracts content from a specific URL, and search_and_fetch combines search with automatic fetching. No overlap or ambiguity.
Tool names consistently use snake_case and mostly follow a verb_noun pattern (fetch_url, web_search). The exception is search_and_fetch which uses two verbs, but it still clearly conveys its combined functionality.
With 3 tools, the set is on the smaller side but still covers the core needs of web searching and URL fetching. It feels slightly minimal but not insufficient for the stated purpose.
The tool surface covers searching, fetching individual pages, and a combined operation. Minor gaps like lacking custom search parameters or batch fetching exist, but the core workflow is functional.