mcp-deepseek-search
Related Servers
Alternatives to mcp-deepseek-search
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes DeepSeek's search and fetch APIs as two MCP tools, letting any MCP-compatible AI agent perform web search with relevance and authority scores, then retrieve chosen pages as Markdown.82 npmMIT
- 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.2677 npm1MIT
- AlicenseAqualityCmaintenanceExposes DeepSeek's Search and Fetch REST APIs as two read-only MCP tools, letting any MCP-capable agent run ranked web searches and retrieve individual pages as truncated Markdown. Works with whichever model the host runs, over stdio or Streamable HTTP.2MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to run web searches that return ranked results with titles, URLs, snippets, summaries, and optional extracted page content, and to fetch HTTP or HTTPS pages as Markdown. It runs over stdio as a zero-dependency Python server that uses DeepSeek's official APIs and any supported MCP client.22MIT
- 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.331 npm1MIT
- AlicenseAqualityBmaintenanceEnables 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.287 npmApache 2.0
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: deepseek_search performs ranked web search, while deepseek_fetch retrieves and converts a single page to Markdown. The description even states fetch should be used after search, eliminating ambiguity.
Both tools follow a consistent deepseek_<verb> pattern (search, fetch). The naming is predictable and easy to reason about.
Two tools is slightly below the typical 3-15 range, but the server has a narrow search-and-fetch purpose where each tool earns its place. No unnecessary tools are included.
The surface covers the full search/read workflow: query with advanced syntax and optional content, then fetch full page content for a specific URL. There are no obvious dead ends for a web search server.