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
      885 npm
      355
      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.
      73 npm
      23
      MIT
    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

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools, web_search and web_extract, have clearly distinct purposes: one performs searches, the other extracts content from a given URL. No overlap or ambiguity exists.

    Naming Consistency5/5

    Both tools follow a consistent 'web_' prefix followed by a verb: search and extract. This is a clear and predictable pattern.

    Tool Count3/5

    With only 2 tools, the server is on the thin side. While the two tools cover the core search+extract workflow, most servers for this domain offer a few more (e.g., search options, deep links, or cached pages). It's borderline but acceptable for a minimal implementation.

    Completeness5/5

    For a web search and extraction service, these two operations—searching and extracting—form a complete core lifecycle. There are no missing essential operations for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive

    Resources