DeepSeek Web Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_URL | No | URL of your self-hosted SearXNG instance | |
| TAVILY_API_KEY | No | API key for Tavily global search | |
| DEEPSEEK_API_KEY | Yes | API key for DeepSeek (required for web_research) | |
| ANYSEARCH_API_KEY | No | Optional API key for AnySearch; anonymous mode has lower rate limits | |
| OPENROUTER_API_KEY | No | Optional API key for OpenRouter, used for reranking in web_search | |
| DEEPSEEK_SEARCH_BASE_URL | No | Base URL for the Anthropic SDK; the SDK appends /v1/messages automatically | https://api.deepseek.com/anthropic |
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 |
|---|---|
| web_searchC | Search the live web and return normalized, citeable sources. |
| web_researchC | Use DeepSeek native web search to research a question and return citeable sources. |
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
Both `web_search` and `web_research` say they search the live web and return citeable sources, so an agent has little basis to choose between them. The descriptions overlap heavily and do not clearly define a simple-search versus deep-research boundary.
Both tool names follow the same lowercase `web_<verb>` pattern, which is predictable and consistent. Although `search` and `research` are semantically close, the naming convention itself is uniform.
Two tools is on the thin side for a web search server, and the second tool appears to be a near-duplicate of the first. Still, two tools is a defensible minimal set for a simple query-and-results workflow.
The server covers basic live-web searching and question-style research, but there are no tools for fetching specific URLs, filtering results, or managing research sessions. Deeper research workflows would likely need workarounds.