Skip to main content
Glama
robbyczgw-cla

web-search-plus-mcp

by robbyczgw-cla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to web-search-plus-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-omnisearch

      spences10
      A
      license
      A
      quality
      A
      maintenance
      🔍 A Model Context Protocol (MCP) server providing unified access to multiple search engines (Tavily, Brave, Kagi), AI tools (Perplexity, FastGPT), and content processing services (Jina AI, Kagi). Combines search, AI responses, content processing, and enhancement features through a single interface.
      3
      159 npm
      351
      MIT

    • SearXNG MCP Server

      tisDDM
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to perform web searches using SearXNG, a privacy-respecting metasearch engine.
      1
      43
      MIT

    • MCP Search Server

      youill0317
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A unified Model Context Protocol server that integrates multiple search providers including Brave, Tavily, Exa, Semantic Scholar, and arXiv. It enables users to perform web, news, and image searches alongside academic research and citation analysis through a single interface.
      -

    • Nexus MCP Server

      adawalli
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Model Context Protocol server that brings AI-powered web search directly into development environments, providing intelligent search results with proper citations in Claude Desktop, Cursor, or any MCP-compatible client.
      79 npm
      23
      MIT
    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

    A3.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have distinct purposes: web_search finds web content, while web_extract retrieves content from a specific URL. There is no overlap in their core actions.

    Naming Consistency5/5

    Both tool names follow the same web_verb pattern, with clear and predictable naming. The convention is consistent and readable.

    Tool Count3/5

    With only two tools, the server sits at the borderline of being too thin. The two tools are individually useful, but the small count suggests a narrow scope.

    Completeness4/5

    The server covers the two core operations one would expect for a web search and extraction service. Minor gaps like search result pagination or provider selection details exist but are not critical.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources