deepseek-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DS_API_KEY | Yes | Your DeepSeek API Key (replace sk-xxxx with your own key) |
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 |
|---|---|
| searchC | 搜索网页 |
| fetchC | 抓取网页,返回页面标题与 Markdown 格式的内容 |
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
search and fetch have clearly distinct purposes: one locates web results, the other retrieves a specific page's content. There is no meaningful overlap in how an agent would select between them.
Both names are lowercase single verbs, which is consistent and readable. However, there is no object/noun component to make the pattern as predictable as a verb_noun convention.
Two tools is slightly thin, but this server has a narrowly scoped search-and-fetch purpose where each tool clearly earns its place. It is not excessive or confusing.
The core lifecycle of web search followed by page retrieval is covered. Minor gaps exist, such as filtering, pagination, or batch retrieval, but agents can still accomplish the main use cases.