Skip to main content
Glama
ds-websearch-mcp

ds-websearch-mcp

by prepaser

Related Servers

Alternatives to ds-websearch-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Exposes 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.
      2
      101 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      2
      677 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to perform web searches and fetch HTTP(S) pages as Markdown through Search and Fetch APIs.
      2
      63 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 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 npm
      MIT

    TDQS

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    Both names are single lowercase verbs (search, fetch), following a consistent verb-only convention. There are no mixed styles or inconsistent patterns.

    Tool Count4/5

    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.

    Completeness5/5

    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.