fetch-mcp
Related Servers
Alternatives to fetch-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables 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.197MIT
- AlicenseBqualityDmaintenanceEnables fetching and converting web content to markdown with built-in prompt injection safeguards that detect and block malicious content attempting to manipulate the LLM.12MIT
- AlicenseAqualityCmaintenanceEnables 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.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to read public webpages as Markdown or HTML, discover links, extract structured JSON, and perform bounded crawls.AGPL 3.0
- AlicenseAqualityBmaintenanceEnables 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.21MIT

JsonLink MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI agents to read any web page as clean Markdown, pull title/description/preview metadata, capture desktop, mobile, or full-page screenshots, and list every link or image on a URL. JavaScript-heavy pages are rendered in a real browser and blocked requests retried through a proxy, so agents can reach content they'd otherwise miss.561 npmMIT
TDQS
Scored across 15 tools
The seven http_* verb tools are unambiguously separated by method, and fetch_meta/fetch_links/fetch_feed/fetch_sitemap/fetch_robots each target a distinct artifact. The only real overlap is the trio fetch_html_to_markdown, fetch_html_to_text, and fetch_reader, which all GET an HTML page and return readable content — the descriptions differentiate them (output format vs. article-body extraction), but an agent may still deliberate over which to pick.
All names are snake_case and follow a clean two-prefix scheme: http_<method> for raw requests and fetch_<artifact> for extraction helpers. The pattern is predictable and self-documenting across all 15 tools.
15 tools sits at the top of the well-scoped range and each one maps to a distinct HTTP method or extraction target. Nothing appears redundant filler, and the verb set (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS) plus a small extraction suite is proportionate to a fetch server's purpose.
HTTP verb coverage is essentially complete (TRACE omitted, which is fine) and the parsing surface covers HTML, metadata, links, feeds, sitemaps, and robots.txt. Minor gaps: no explicit binary/raw-byte download tool, no form-urlencoded or multipart POST helper, and no cookie/session handling for multi-step flows.