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.
      171
      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

    • 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

    • rasterly-mcp

      rasterly-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read, screenshot, or convert web pages to PDF using a real headless browser, turning any URL into clean Markdown, a visual image, or a print-ready document.
      82 npm
      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

    A4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes: raw HTTP verbs vs. content transforms vs. site metadata. The only possible confusion is fetch_reader and fetch_html_to_markdown, since both return markdown from a URL, though their article-focused vs. document-focused intent is described well.

    Naming Consistency3/5

    The HTTP verbs are consistently named http_get/http_post/etc., and most fetch tools follow a fetch_ resource pattern. But fetch_reader does not match fetch_html_to_markdown or fetch_html_to_text, and the file uses two overlapping prefixes, making the overall naming scheme feel mixed rather than fully consistent.

    Tool Count5/5

    15 tools is within the upper edge of a well-scoped server, and each tool addresses a meaningful fetch or extraction task: HTTP methods, markdown/text conversion, metadata, links, robots, sitemaps, and feeds. No tool feels redundant or gratuitous.

    Completeness5/5

    The server covers the full lifecycle of fetching and interpreting web resources: all standard HTTP methods, article extraction, general HTML conversion, raw text, metadata, links, robots.txt, sitemaps, and feed parsing. The surface is comprehensive for its stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources