Skip to main content
Glama
StarkL

DeepSeek Search MCP Server

by StarkL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to DeepSeek Search MCP Server

No user-submitted related servers found.

    Related Servers

    • CrawlEyes

      waiky-github
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to perform web searches and extract full-text content from web pages via standard MCP tools, with fallback search and semantic reranking.
      2
      2
      MIT

    • DeepSeek Search MCP

      CaelixOrbit
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to run web searches via DeepSeek's open platform API, with optional web page fetching that returns Markdown content, and supports query syntax for source, language, and time filters.
      1
      MIT

    • MyWebSearch MCP

      iuiu-py
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform unified web research through a single MCP server, including search, page fetching, recursive crawling, document parsing, YouTube transcript extraction, and deep multi-query research.
      3
      -

    • DeepSeek Search MCP

      evilwk
      A
      license
      A
      quality
      C
      maintenance
      Exposes 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.
      2
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    deepseek_search and deepseek_fetch have clearly distinct purposes: one queries the search engine, the other retrieves and converts a specific URL to Markdown. An agent can trivially tell which to call based on whether it has a query or a known URL.

    Naming Consistency5/5

    Both tools use the same deepseek_ prefix followed by a concise action verb (search, fetch). The pattern is predictable and readable, with no mixing of conventions.

    Tool Count4/5

    Two tools is on the lean side, but for a web-retrieval server this is exactly the minimal complete pair (find then read). Nothing feels missing or padded, though a multi-URL or batch fetch would be a natural addition.

    Completeness5/5

    Search plus fetch covers the full retrieval lifecycle: discovering sources and then reading them in depth. There are no obvious dead ends for the stated purpose of web search and content extraction.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources