Skip to main content
Glama
evilwk

DeepSeek Search MCP

by evilwk

Related Servers

Alternatives to DeepSeek Search MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to search the live web and fetch any URL as clean text through Ollama's web search and fetch APIs, returning ranked results with page text and outgoing links. Runs as a single dependency-free stdio server, so agents can ground their answers with current web content without a separate search vendor.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to search the web and fetch individual pages through two stdio tools, returning ranked results or extracted page content, titles and outbound links. It wraps a hosted, API-key-authenticated service (or a local daemon) with zero runtime dependencies.
      14 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to run local deep-research workflows via a single MCP stdio server, combining web search, page extraction, query-aware distillation, and caching without cloud quotas. It exposes tools for deep research, search, and single or batch URL reading.
      6
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes web_search and web_fetch tools, allowing LLM applications to search the web via DuckDuckGo and fetch page content as cleaned markdown.
      -
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that provides web search powered by DeepSeek's native search API, returning AI-generated answers with source links. Integrates with MCP-compatible clients like Claude Code and Cursor.
      1
      MIT

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    Search and fetch target clearly different operations: search returns ranked results, while fetch retrieves a single page's full content. The descriptions reinforce the intended use sequence (search then fetch), leaving no meaningful ambiguity.

    Naming Consistency5/5

    Both tool names are simple lowercase verbs (search, fetch), following a consistent single-verb convention. There is no mixing of styles or noun phrasing.

    Tool Count4/5

    Two tools is slightly below the typical 3–15 range, but each is well-scoped and earns its place for a focused web search and retrieval server. The surface is minimal yet sufficient for the core workflow.

    Completeness5/5

    The server is read-only, and its domain lifecycle is search then fetch; both operations are present with useful filtering parameters. No obvious gaps exist for basic web search and page retrieval.