Skip to main content
Glama
Doriandarko

Claude Web Search MCP Server

by Doriandarko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Claude Web Search MCP Server

No user-submitted related servers found.

    Related Servers

    • searxng-mcpb

      danchev
      A
      license
      A
      quality
      C
      maintenance
      Adds web search to Claude Desktop through a user-selected SearXNG instance, with engine and category selection, language and time-range filters, and bounded result counts.
      1
      AGPL 3.0

    • Perplexity MCP Server

      jaacob
      A
      license
      B
      quality
      D
      maintenance
      Facilitates web search capabilities using Perplexity's API, allowing users to retrieve search results through Claude's interface.
      1
      8
      MIT

    • Brave Search MCP Server

      cuer-bot
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables web search via Brave Search API with freshness filters, full page content fetching, and usage tracking. Designed for Claude integration.
      343 npm
      GPL 3.0

    • Perplexity MCP Server

      shaunmacfullstack
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Perplexity AI's search capabilities to Claude, enabling real-time web search and information retrieval within the assistant. The project is currently in active development with plans to support Perplexity Spaces and multi-source data synthesis.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    The single tool name 'web_search' follows a consistent verb_noun pattern, and since there are no other tools, there is no inconsistency to evaluate. The naming is straightforward and appropriate for its function.

    Tool Count2/5

    A single tool is generally too few for most server purposes, as it limits functionality and can feel thin or incomplete. For a web search server, while the core function is covered, additional tools like advanced search filters or result management might be expected to enhance utility.

    Completeness3/5

    The server provides a basic search function, which covers the essential need for real-time information retrieval. However, there are notable gaps, such as lack of tools for refining searches, handling pagination, or accessing specific types of content, which could limit agent effectiveness in complex scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources