MCP01: Google HTML Fetcher MCP Server
Related Servers
Alternatives to MCP01: Google HTML Fetcher MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to save public articles, papers, images, videos, podcasts, and subtitles as local files, with support for multiple sources and output formats.MIT
- FlicenseBqualityDmaintenanceEnables fetching visible text content and extracting all links from web pages through URL requests. Designed specifically for LM Studio integration to provide web scraping capabilities.22-
- AlicenseAqualityDmaintenanceEnables AI assistants to download files from HTTP/HTTPS URLs to local directories or file paths with options like custom filename, headers, and overwrite control.110 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and IDE workflows to fetch and crawl webpages locally, extracting readable content and converting it to token-efficient Markdown with preserved links.MIT
- AlicenseNot gradedqualityDmaintenanceFetches web content and returns it in HTML, JSON, plain text, or Markdown format.5,878 npmMIT
- AlicenseBqualityDmaintenanceEnables LLMs to retrieve and process web content by fetching URLs and converting HTML to markdown format. Supports chunked reading of large pages and can access both public websites and local networks.1MIT
TDQS
Scored across 1 tool
With only one tool in the set, there is no possibility of overlap or misselection. The single tool's purpose (fetch google.com HTML and save it to disk) is unambiguous.
The lone name fetch_google_html follows a clean snake_case verb_noun pattern. There are no other names to conflict with, so consistency is trivially satisfied.
A single tool is borderline thin even for a narrowly scoped fetcher, and it bundles fetching plus file storage into one opaque operation. The scope is small enough that one tool is defensible, but it feels under-built.
The tool hardcodes google.com and a local Windows path, and there is no companion tool to read, list, or delete the stored HTML, so an agent cannot retrieve the fetched content. Coverage of even this tiny domain has a dead end at the output stage.