A
licenseA
qualityC
maintenanceAn MCP server for fetching and transforming web content into various formats.
4
8
MIT
huoshui-fetch
by huoshuiai42
Related Servers
Alternatives to huoshui-fetch
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA powerful MCP server for fetching and transforming web content into various formats (HTML, JSON, Markdown, Plain Text) with ease.44,875 npm42MIT
- AlicenseAqualityCmaintenanceMCP server that provides web content fetching, summarization, comparison, and extraction capabilities, handling up to 20 URLs per request.330 npm8MIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server for web content extraction that converts HTML pages into clean, LLM-optimized Markdown using Mozilla's Readability. It supports batch processing, intelligent multi-page crawling, and configurable caching while respecting robots.txt standards.33 npm-
- AlicenseNot gradedqualityBmaintenanceA web fetching MCP server with HTTP proxy support, allowing AI to retrieve web content in markdown, text, or HTML format while handling anti-crawler detection and redirects.1,026 npm1MIT
- AlicenseAqualityBmaintenanceAn MCP server that fetches web pages and extracts clean, AI-usable context from them, enabling tools for link discovery, content search, and integrated fetch-and-search operations.513 npm1MIT
TDQS
A3.8/5.0
Scored across 11 tools
Disambiguation4/5
The fetch tools fetch_url and fetch_with_headers are highly similar, differing only in the ability to pass custom headers, which could lead to confusion about which to use. The extraction and conversion tools are all clearly distinct in their outputs, so mis-selection is unlikely for those.
Naming Consistency3/5
Naming conventions are mixed: fetch_url and fetch_with_headers lack the '_tool' suffix that appears on all other tools, and there is no uniform prefix pattern. However, the 'extract_' and 'html_to_' groups are internally consistent, making the set readable overall.
Tool Count5/5
With 11 tools, the server is well-scoped for a web fetching and processing utility. Each tool serves a distinct purpose in the pipeline, and the count is neither excessive nor too sparse for the stated functionality.
Completeness4/5
The tool surface covers the complete workflow of fetching, cleaning, converting, and extracting content from web pages. Minor gaps exist, such as the lack of cookie/session handling or CSS selector-based extraction, but these are not essential to the core purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues