deepseek-search-mcp
Related Servers
Alternatives to deepseek-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables web search and page fetching through the DeepSeek Search and Fetch APIs, exposing search and fetch tools to MCP clients. Supports paginated content retrieval with cursors so long pages can be read in chunks without repeating upstream requests.252 npmAGPL 3.0
- 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
- 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
- AlicenseAqualityCmaintenanceEnables agents to run web searches with query operators and to fetch web pages as Markdown through DeepSeek's native Search/Fetch JSON API. It acts as a fallback for hosts whose built-in web tools are unavailable or return errors such as HTTP 403, rather than retrying them repeatedly.21MIT
- AlicenseAqualityBmaintenanceEnables AI agents to perform real-time web search and fetch/parse webpages into clean Markdown through DeepSeek's Search and Fetch APIs. It provides configurable summaries, scoring, and robust retries for integration with MCP-compatible assistants.21MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: web_search retrieves ranked results from a query, while web_fetch reads a single known URL into Markdown. The web_fetch description even explicitly states when to prefer it over search, eliminating any selection ambiguity.
Both tools follow the same predictable snake_case verb_noun pattern (web_search, web_fetch) with a shared 'web_' prefix. No inconsistency or mixed conventions.
Two tools is minimal, but for a search-centric server the search-plus-fetch loop is exactly the required surface, and neither tool is redundant. It sits just below a richer surface that could add pagination or multi-URL fetching.
The core retrieve-then-read workflow is fully covered, and search operators are folded into the query string rather than requiring extra tools. Minor gaps exist such as no paging/count control or batch fetching, but agents can work around these.