fetchmcp
Related Servers
Alternatives to fetchmcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConverts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.MIT
- AlicenseNot gradedqualityAmaintenanceFetches webpages and converts them into clean, token-efficient Markdown, optionally crawling multiple linked pages while respecting robots.txt and caching results for AI agents and LLM pipelines.MIT
- AlicenseNot gradedqualityDmaintenanceFetches web pages and converts them to markdown for LLM consumption, supporting chunked reading and raw content extraction.MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.-
- AlicenseNot gradedqualityAmaintenanceFetches webpages and converts them into clean Markdown for token-efficient scraping by AI agents, preserving links and supporting configurable multi-page crawling, caching, and robots.txt-aware rate limiting.MIT
- AlicenseNot gradedqualityDmaintenanceConverts URLs into clean, LLM-ready markdown, respecting robots.txt and never bypassing anti-bot measures or paywalls.MIT
TDQS
Scored across 2 tools
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.
Both tools follow the same verb_noun pattern (read_url, read_docs), making the naming predictable and intuitive. No mixed conventions or vague verbs.
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.
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.