Skip to main content
Glama
TheSethRose

Fetch Browser

by TheSethRose
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Fetch Browser

No user-submitted related servers found.

    Related Servers

    • Wick by wickproject

      Wickofficial

      wickproject
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides browser-grade web access for AI agents, using Chrome's actual network stack to bypass anti-bot protections and return clean markdown.
      9
      -

    • mult-fetch-mcp-server

      lmcc-dev
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.
      5
      27 npm
      15
      MIT

    • Local Browser MCP

      nolanbaxter
      A
      license
      B
      quality
      A
      maintenance
      A headless, agent-controllable real browser as an MCP server that enables AI agents to navigate, click, fill, eval JavaScript, and take screenshots on localhost and allowed hosts, with no GUI required.
      27
      4
      MIT

    • Groundlane

      lanefoundry
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents controlled access to the web, offering unified tools for fetching pages as Markdown, searching across multiple providers, and extracting structured data via CSS selectors.
      Apache 2.0

    • krwl3r

      garciarsdiego
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.
      1
      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

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: fetch_url retrieves content from a specific URL, while google_search performs web searches and returns results. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.

    Naming Consistency4/5

    Both tools follow a verb_noun pattern (fetch_url, google_search), which is consistent and predictable. The minor deviation is that google_search includes a brand name, but this does not break the overall naming convention.

    Tool Count3/5

    With only 2 tools, the server feels thin for a browser-related purpose, as it lacks common operations like navigating pages, handling cookies, or interacting with web elements. However, the tools provided are core functionalities, so it's borderline appropriate.

    Completeness2/5

    For a browser server, there are significant gaps in coverage, such as no tools for page navigation, form submission, JavaScript execution, or session management. The surface is severely incomplete for typical browser automation tasks, limiting agent effectiveness.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources