Skip to main content
Glama
Sign In
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
      256 npm
      358
      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
      C
      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.
      131 npm
      22
      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

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: web_search finds sources via providers, while web_extract pulls content from a specific URL. There is no meaningful overlap in intent or expected inputs.

    Naming Consistency5/5

    Both names follow a consistent web_<verb> snake_case pattern that directly reflects their actions. The convention is predictable and easy for an agent to infer.

    Tool Count3/5

    Two tools is thin for a server that also exposes provider routing and detail modes, even if the core surface is intentionally focused. It is borderline rather than clearly over- or under-scoped.

    Completeness4/5

    Search and extraction cover the primary web-research workflow without dead ends. Minor gaps exist around batch operations or provider introspection, but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources