Skip to main content
Glama
YawLabs

fetch-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to fetch-mcp

No user-submitted related servers found.

    Related Servers

    • Crawlberg MCP Server

      xberg-io
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to crawl and scrape websites, converting HTML to clean Markdown and structured metadata with support for JavaScript rendering, bot evasion, and SSRF protection.
      181
      MIT

    • Safer Fetch MCP Server

      Tommertom
      A
      license
      B
      quality
      D
      maintenance
      Enables fetching and converting web content to markdown with built-in prompt injection safeguards that detect and block malicious content attempting to manipulate the LLM.
      1
      2
      MIT

    • fluxio-mcp

      IYABAO
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to read RSS/Atom feeds, extract web page content as text or Markdown, search the web, and batch-fetch multiple URLs without building custom crawlers.
      5
      MIT

    • scrape-mcp

      guanyuyan
      A
      license
      A
      quality
      A
      maintenance
      Enables AI models to fetch real web pages while automatically bypassing anti-bot protections, login walls, and JS rendering, then returns clean, token-efficient article content.
      4
      MIT

    • cleanfetch

      belzorash
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to read web pages reliably, returning clean markdown content, hyperlinks, and metadata without navigation or ad noise.
      3
      6 npm
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools are clearly distinct (each HTTP method, and each fetch utility has a unique purpose). The three HTML conversion tools (fetch_reader, fetch_html_to_markdown, fetch_html_to_text) have overlapping goals but are differentiated by output format and focus (main article vs full page vs plain text). This slight ambiguity prevents a perfect score.

    Naming Consistency4/5

    Tools follow two clear prefixes: http_ for raw HTTP methods and fetch_ for high-level fetch operations. Within each group, naming is consistent (e.g., http_get, http_post; fetch_meta, fetch_links). The mixed prefixes are intentional and predictable, but not a single uniform convention, so a 4 is appropriate.

    Tool Count5/5

    15 tools is within the ideal range and each tool addresses a distinct need: seven HTTP methods and eight fetch utilities (reader, markdown, text, robots, sitemap, meta, links, feed). No tool feels redundant; the count is well-scoped for a comprehensive fetch/HTTP server.

    Completeness5/5

    The tool surface is complete for the domain: all standard HTTP methods are covered, and the fetch tools cover common web scraping needs (reading, converting, metadata, links, robots, sitemaps, feeds). There are no obvious gaps that would cause agent failures; http_get provides raw access when needed.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources