WebFetch.MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| web_searchA | Search the web using a local SearxNG instance. Returns search results with titles, URLs, and snippets. |
| web_fetchA | Fetch and extract readable content from a web page URL using Mozilla Readability. |
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 clearly distinct purposes: one searches the web, the other fetches a specific page. There is no overlap or ambiguity.
Both tools follow the same verb_noun pattern with snake_case: web_search and web_fetch. The naming is perfectly consistent.
With only 2 tools, the set is minimal but still appropriate for the server's focused purpose of web search and content fetching. It is not excessive or overly thin.
The tool set covers the core operations for web interaction: searching and fetching. While there could be additional tools like raw HTML fetching or link checking, the current scope is reasonably complete.