deepseek-search
Related Servers
Alternatives to deepseek-search
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search the web and fetch public web pages via DeepSeek's Search and Fetch APIs, returning ranked results and Markdown page content for agent use.MIT
- 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.87 npm2MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to run web searches via DeepSeek's open platform API, with optional web page fetching that returns Markdown content, and supports query syntax for source, language, and time filters.188 npm1MIT
- 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
- 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
TDQS
Scored across 2 tools
The two tools split cleanly along the search/read axis: web_search discovers sources, web_fetch reads a single page in full. The descriptions explicitly cross-reference each other ('Follow up with web_fetch', 'a url returned by web_search'), leaving no realistic misselection risk.
Both names use the same web_<action> pattern (web_search, web_fetch), same style, same prefix, unambiguous verbs. Fully predictable.
Two tools is on the thin side per the general guidance, but for a search server this is exactly the minimal viable pair—search then fetch—and each tool clearly earns its place with no filler.
Search plus full-page fetch covers the core discover-then-read lifecycle for a web search domain, with operators documented for refinement. Minor gaps exist (e.g. no batch/multi-URL fetch or crawl), but agents can work around them by calling web_fetch repeatedly.