Skip to main content
Glama
NeoXider

Web Search Neo

by NeoXider
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Web Search Neo

No user-submitted related servers found.

    Related Servers

    • Tagny MCP Server

      tagny
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables web browsing capabilities for locally served LLMs through URL text fetching, link extraction, and web search using Brave and DuckDuckGo engines. Designed to enhance LLMs with real-time web access through the MCP protocol.
      MIT

    • mcp-web-search

      tolstikov-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables web search, page fetching and cleaning, OCR from images, and broken-link checking through MCP tools, with multi-provider aggregation, caching, and anti-detection features.
      19 npm
      MIT

    • CrawlEyes

      waiky-github
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to perform web searches and extract full-text content from web pages via standard MCP tools, with fallback search and semantic reranking.
      2
      2
      MIT

    • Fetchkeep

      rayorole
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to fetch web pages, extract clean Markdown, save and search versions offline, crawl sites within bounds, and retrieve stable citations through MCP tools.
      9 npm
      Apache 2.0
    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.6/5.0

    Scored across 2 tools

    Disambiguation4/5

    The split is essentially execute vs. read/inspect: web_action performs ordered browser/search actions, while web_info reads contracts, page/console/network state, and browser/search status. The two responsibilities are mostly distinct, though web_info's broad 'read the page/search state' scope could overlap with results returned by web_action.

    Naming Consistency5/5

    Both tools use a consistent web_<noun> convention: web_action and web_info. The convention is not verb_noun, but it is predictable and uniform across the set.

    Tool Count3/5

    Two tools is below the typical 3-15 range and feels thin, even though web_action is an intentional multiplexer handling many canonical actions. The design avoids tool explosion, but pushes discovery and complexity into arguments and the contract-reading flow.

    Completeness4/5

    A generic action executor plus a contract/state reader can plausibly cover browser/search lifecycle operations, including session use and inspection. However the actual action surface is hidden behind runtime discovery via web_info, so completeness is less self-evident from the exposed tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources