MCP01: Google HTML Fetcher MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_OUTPUT_DIR | No | Directory where HTML files will be saved | C:\Users\hiren\Documents\mcpserver\mcp01 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_google_htmlB | Connects to google.com, fetches the HTML source of the page, and stores it in C:\Users\hiren\Documents\mcpserver\mcp01 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.