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.190MIT
- 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
- AlicenseAqualityBmaintenanceEnables 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
- AlicenseAqualityAmaintenanceEnables 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.8MIT

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.5257 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to fetch public web pages and return their main content as clean Markdown, including JavaScript-rendered pages with navigation, ads, and boilerplate stripped. Supports OAuth sign-in and a read-only tool for pulling docs, articles, and product pages into chat or knowledge bases.237 npmMIT
TDQS
Scored across 15 tools
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.
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.
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.
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.