DeepSeek Search MCP
Related Servers
Alternatives to DeepSeek Search MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables MCP-capable AI clients to run web searches through DeepSeek's search engine and fetch individual webpages as Markdown. Search results include relevance scores, authority, and publication times, and support advanced query syntax such as site:, lang:, and date filters.239 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to run web searches and fetch individual web pages as Markdown through DeepSeek's official Search/Fetch API, with freshness filtering, structured metadata such as publish date, authority and rerank scores, and raw structured output.129 npm2MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to run ranked web searches with DeepSeek's search operators and to retrieve pages as titles and Markdown through DeepSeek's official Search and Fetch APIs, without invoking a chat model. Results are returned as structured content plus matching JSON text, with options for result count, page content, localization, and original-question context.250 npm3MIT
- AlicenseAqualityDmaintenanceExposes DeepSeek's web search and page-fetch tools to any MCP client, letting any LLM run searches with quality signals like rerank score and source authority, plus advanced query syntax. It also retrieves single pages as Markdown, with built-in throttling, retries, and size-conscious summaries.2133 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to perform DeepSeek-native web searches through the Anthropic-compatible Messages endpoint, returning summarized results with cited sources.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to run web searches and fetch HTTP(S) pages as Markdown via the DeepSeek Search/Fetch API, returning titles, URLs, summaries, publication dates, authority scores, and optional page content. Supports advanced query operators like site:, exact phrases, exclusion terms, lang:, and date-range filters, with retries, timeouts, and structured errors.1MIT
TDQS
Scored across 1 tool
With a single tool there is no possibility of misselection or overlap; its purpose is unambiguous. The name and description align cleanly, leaving nothing to confuse.
The lone tool uses a clear snake_case verb_noun style (deepseek_search) that matches its server identity. No mixed conventions exist since there is only one name.
A one-tool surface is borderline thin even for a search server; typical search MCPs expose pagination, filtering, or multiple content types. It works but leaves little room for user control.
Core web search is covered, but there are no options for result count, pagination, freshness, or filtering, which are common expectations. The surface is functional yet notably shallow for a search domain.