Skip to main content
Glama
fangsylar-pixel

browser-search-mcp

by fangsylar-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to browser-search-mcp

No user-submitted related servers found.

    Related Servers

    • Google Search Tool

      iwanghc
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to perform real-time Google searches with anti-bot protection. Bypasses search engine restrictions using advanced browser automation to extract search results locally without requiring paid API services.
      7
      MIT

    • Bright Data Web MCP

      dsouza-anush
      A
      license
      B
      quality
      D
      maintenance
      Enables LLMs and AI agents to access real-time web data, search websites, and navigate the web without getting blocked. Includes 5,000 free monthly requests and supports web scraping, browser automation, and bypassing geo-restrictions.
      60
      7,869
      1
      MIT

    • webscout-mcp

      wxs-lang
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to perform web searches, fetch and extract page content, and crawl sites with caching, rate limiting, and robots.txt compliance, all without needing API keys.
      11
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    web_search and web_search_multi are related but clearly separated by the multi-engine behavior. web_search_status and web_search_discover_browsers overlap somewhat in browser inspection, but their purposes remain distinct. web_search_read_page is unambiguous.

    Naming Consistency4/5

    Most tools use the web_search_ prefix with descriptive suffixes like multi, read_page, status, and discover_browsers. The base web_search tool lacks a suffix, but the pattern remains predictable and readable overall.

    Tool Count5/5

    Five tools is well-scoped for a browser-based search server. Search, multi-engine search, page reading, status, and browser discovery each earn their place without unnecessary overlap or bloat.

    Completeness4/5

    The core workflow of searching, combining results, and reading pages is well covered. Browser status and discovery support the environment side. Minor gaps like explicit browser launch/close management exist, but they are outside the apparent search-focused purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources