web-fetch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAVILY_API_KEY | Yes | Tavily API key for web fetch and search | |
| WEB_FETCH_PROXY | No | Optional proxy URL for outbound requests if direct access fails | |
| FIRECRAWL_API_KEY | No | Optional Firecrawl API key for fallback in web fetch |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_fetchA | Fetch and extract the content of a web page as markdown (or plain text). Tries Tavily first; on failure or empty result, automatically falls back to Firecrawl. Requires TAVILY_API_KEY and/or FIRECRAWL_API_KEY in the server's environment. |
| web_searchA | Search the web with Tavily and return titles, URLs, and snippets (plus an optional synthesized answer). No fallback — requires TAVILY_API_KEY in the server's environment. |
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 2 tools
The two tools have distinct purposes: web_fetch retrieves content from a specific URL, while web_search performs a web search query. There is no overlap in functionality.
Both tools follow the same verb_noun pattern with snake_case (web_fetch, web_search), making the naming predictable and consistent.
With only 2 tools, the server is minimal but appropriate for its narrow scope of web fetching and searching. It could be expanded, but it's not overly thin for a focused utility.
The tool surface covers the basic needs of fetching a web page and searching the web. Minor gaps exist, such as no batch fetching or support for additional output formats, but no critical operations are missing.