web-fetch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PROXY | No | Optional HTTP proxy for network access issues. | |
| HTTPS_PROXY | No | Optional HTTPS proxy for network access issues. | |
| GEMINI_API_KEY | Yes | A valid Gemini API key for the server to work. |
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 |
|---|---|
| summarize_webC | Summarize content from one or more URLs |
| compare_webB | Compare content from multiple URLs |
| extract_webC | Extract specific information from web content based on natural language prompts |
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 3 tools
Each tool has a clearly distinct purpose: summarize gives an overview, compare contrasts multiple URLs, and extract pulls specific details. No ambiguity between them.
All tool names follow the same verb_web pattern (summarize_web, compare_web, extract_web), making the set predictable and easy to navigate.
Three tools is appropriately scoped for a web-content analysis server. Each tool addresses a distinct need without unnecessary bloat.
The toolset covers the core operations of summarization, comparison, and extraction. A minor gap is the absence of a raw fetch tool, but the server's purpose is focused on processed output, so this is acceptable.