MCP Deep Web Research Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | info |
| TIMEOUT_MS | No | Request timeout in milliseconds | 55000 |
| MAX_RETRIES | No | Number of retry attempts for failed requests | 3 |
| SEARCH_DELAY_MS | No | Delay between searches in milliseconds | 200 |
| MAX_PARALLEL_SEARCHES | No | Maximum number of concurrent searches | 5 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deep_researchC | Perform deep research on a topic with content extraction and analysis |
| parallel_searchC | Perform multiple Google searches in parallel |
| visit_pageC | Visit a webpage and extract its content |
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 has a clearly distinct purpose: deep_research focuses on comprehensive topic analysis, parallel_search handles multiple Google searches, and visit_page extracts content from specific webpages. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming is mixed: deep_research and parallel_search use snake_case with descriptive names, while visit_page also uses snake_case but is more action-oriented. There is no consistent verb_noun pattern, but the names are still readable and understandable.
With only 3 tools, the server feels thin for a 'Deep Web Research' scope, which might imply more comprehensive capabilities like data analysis or report generation. However, the tools cover core search and extraction tasks, so it's borderline but not severely lacking.
The tools cover basic web research tasks (searching, visiting, deep analysis), but there are notable gaps such as no tools for saving results, managing research sessions, or advanced data processing. Agents can work around this, but the surface is not fully comprehensive for deep web research.