Skip to main content
Glama
xinzhuang

deepseek-websearch-mcp

by xinzhuang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to deepseek-websearch-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • DeepSeek Search MCP Server

      StarkL
      A
      license
      A
      quality
      A
      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
      1
      MIT

    • deepseek-search

      zou-hong-run
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to run web searches with query operators and to fetch web pages as Markdown through DeepSeek's native Search/Fetch JSON API. It acts as a fallback for hosts whose built-in web tools are unavailable or return errors such as HTTP 403, rather than retrying them repeatedly.
      MIT

    • DeepSearch MCP

      yuemingruoan
      A
      license
      B
      quality
      C
      maintenance
      Enables web search and site-specific search capabilities through the Deepsearch model. Provides unified access to broad web retrieval and targeted site search functionality within the MCP ecosystem.
      2
      19 npm
      5
      Apache 2.0
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    web_search and web_fetch have clearly distinct purposes: one searches, the other retrieves page content. No overlap in function, and descriptions explicitly reference how they complement each other.

    Naming Consistency5/5

    Both tool names follow a consistent snake_case verb_noun pattern with a shared 'web_' prefix, making the relationship and action clear.

    Tool Count3/5

    With only 2 tools, the set is thin for a websearch server. While each tool earns its place, the absence of additional operations (e.g., batch fetch or result pagination) makes the count borderline.

    Completeness4/5

    The core workflow of searching and fetching pages is covered, and search syntax is rich. Minor gaps like batch fetching or advanced result filtering keep it from being fully complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources