Skip to main content
Glama
everford

Fetcher MCP

by everford
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Fetcher MCP

No user-submitted related servers found.

    Related Servers

    • Fetch MCP

      jae-jae
      A
      license
      B
      quality
      F
      maintenance
      An MCP server that retrieves web page content using Playwright headless browser, capable of extracting main content and converting to Markdown format.
      3
      3,627 npm
      1,087
      MIT

    • Browser MCP Server

      sac916
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to automate web browsers through Playwright, providing capabilities for navigation, content extraction, form filling, screenshot capture, and JavaScript execution. Supports multiple browser engines with comprehensive error handling and security features.
      1
      -

    • Playwright Server MCP

      ziux
      A
      license
      B
      quality
      D
      maintenance
      A browser automation server providing Playwright capabilities for controlling web browsers, capturing screenshots, extracting content, and performing complex interactions through an MCP interface.
      6
      Apache 2.0

    • MCP Web Browser Server

      random-robbie
      A
      license
      A
      quality
      D
      maintenance
      An advanced web browsing server enabling headless browser interactions via a secure API, providing features like navigation, content extraction, element interaction, and screenshot capture.
      6
      27
      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

    C2.9/5.0

    Scored across 2 tools

    Disambiguation3/5

    The two tools have overlapping purposes—both fetch web page content—but the descriptions clarify that one handles a single URL while the other handles multiple URLs. This distinction is clear enough to avoid misselection, but the core functionality is identical, leading to some ambiguity in why they are separate tools.

    Naming Consistency5/5

    The tool names follow a perfectly consistent verb_noun pattern with 'fetch_url' and 'fetch_urls', using snake_case throughout. The naming is predictable and clear, with no deviations in style or convention.

    Tool Count2/5

    With only two tools, the server feels under-scoped for a general-purpose 'Fetcher' domain. A single tool with parameters for single or multiple URLs could suffice, making the current count seem redundant and inefficient for typical agent workflows.

    Completeness2/5

    The tool surface is severely incomplete for web fetching; it lacks essential operations like handling HTTP methods (e.g., POST), managing headers, parsing content, or error handling. Agents will face dead ends when needing more than basic retrieval, causing frequent failures.

    Resources