Skip to main content
Glama
labtoolsstudio

fetchmcp

by labtoolsstudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to fetchmcp

No user-submitted related servers found.

    Related Servers

    • skrape

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      Converts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
      MIT

    • fetch

      RMRanjit
      A
      license
      Not graded
      quality
      D
      maintenance
      Fetches web pages and converts them to markdown for LLM consumption, supporting chunked reading and raw content extraction.
      MIT

    • escalator

      ruslanstarikov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables fetching web pages as clean Markdown with automatic escalation from direct requests to residential proxies and headless browsers to overcome blocks, plus built-in politeness handling like robots.txt and rate limiting.
      -

    • agent-web

      foomworks
      A
      license
      Not graded
      quality
      D
      maintenance
      Converts URLs into clean, LLM-ready markdown, respecting robots.txt and never bypassing anti-bot measures or paywalls.
      MIT

    • WebFetch MCP Server

      Sh1d0w
      F
      license
      Not graded
      quality
      D
      maintenance
      Fetches webpages with JavaScript rendering, converts HTML to clean Markdown for LLM analysis, and uses stealth plugins to avoid bot detection.
      -
    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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: read_url fetches any web page as full content, while read_docs is specifically for documentation pages and strips chrome. The descriptions explicitly call out when to use each, eliminating ambiguity.

    Naming Consistency5/5

    Both tools follow the same verb_noun pattern (read_url, read_docs), making the naming predictable and intuitive. No mixed conventions or vague verbs.

    Tool Count3/5

    With only 2 tools, the server feels slightly thin, but the narrow purpose (fetching and converting web content) justifies such a small surface. It borders on the low end of the ideal range but is not egregiously insufficient.

    Completeness5/5

    The tool set covers the core needs of fetching and reading web content comprehensively: general pages, documentation pages, and handling of multiple formats including JS-rendered content. No obvious missing operations for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources