ds-websearch-mcp
Related Servers
Alternatives to ds-websearch-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityCmaintenanceExposes 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.2101 npm2MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to run web searches and fetch pages, returning structured search results and Markdown page content through two tools.2MIT
- 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
- AlicenseAqualityCmaintenanceEnables MCP clients to perform web searches and fetch HTTP(S) pages as Markdown through Search and Fetch APIs.263 npmMIT
- 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.75 npmMIT
TDQS
Scored across 2 tools
Search is for discovering web results via a query with operators, while fetch is for reading a specific URL or continuing a cached snapshot via cursor. The two tools have clearly distinct roles and no overlapping functionality.
Both names are single lowercase verbs (search, fetch), following a consistent verb-only convention. There are no mixed styles or inconsistent patterns.
Two tools is slightly below the typical 3–15 range, but each earns its place for this narrow search-and-fetch domain. The minimal surface is reasonable rather than thin, given the focused purpose.
Search plus fetch covers the full lifecycle: query the web, then retrieve full page content with pagination via cursors. No obvious gaps exist, and cursor expiry can be handled by re-searching.