DeepSeek Search MCP
Related Servers
Alternatives to DeepSeek Search MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables any MCP-compatible AI agent to search the live web and fetch pages as clean Markdown, including batch fetching with rate limiting, retries, and context-safe truncation.3MIT
- AlicenseAqualityBmaintenanceEnables agents to search the live web and fetch URLs as clean Markdown, returning ranked search results and paginated page content through two lightweight tools.223 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform live web searches with ranked results and extracted page passages, plus clean markdown extraction of any URL.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search the web through configured providers and crawl single pages or entire sites into clean Markdown or JSON, including authenticated crawls and STDIO/HTTP MCP access.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search the web through configured providers and crawl pages or whole sites into clean Markdown or JSON, including authenticated crawls and STDIO/HTTP transport.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search the web through configured providers and crawl single pages or whole sites into clean Markdown or JSON, including content behind logins, over MCP STDIO or HTTP.-
TDQS
Scored across 2 tools
deepseek_search (query the engine, return ranked results) and deepseek_fetch (retrieve a single known URL as Markdown) are cleanly separated discovery vs. retrieval operations with no overlap. The fetch description even states explicitly when to use it after search, eliminating misselection risk.
Both tools follow the same predictable pattern: a shared `deepseek_` namespace prefix plus a short, unambiguous verb (search, fetch). No mixed casing or verb-style drift.
Two tools is thin in absolute terms but this is the canonical minimal surface for a search server — one discovery tool, one retrieval tool, each earning its place with no bloat. Slight under-coverage relative to a fuller web-research surface, but nothing is superfluous.
The domain (web search + page retrieval) is essentially covered end-to-end: rich query syntax, ranking/authority metadata, content extraction, truncation control, and SSRF-style URL validation. Minor gaps remain — no pagination/offset tool to page deeper into results and no batch fetch — but agents can work around both by re-querying or looping fetches.