MCP Fetch With Proxy
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchA | Retrieves URLs from the Internet and extracts their content as markdown. If images are found, their URLs will be included in the response. |
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, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The single tool has a clear and distinct purpose without any competing alternatives.
The single tool name 'fetch' follows a simple verb pattern, and with only one tool, consistency is inherently perfect. There are no other tools to create naming conflicts or inconsistencies.
A single tool is too few for most server purposes, as it limits functionality and flexibility. While it might suffice for basic fetching, it feels thin and under-scoped for a server named 'MCP Fetch With Proxy', which suggests broader capabilities.
The tool surface is severely incomplete; it only provides fetching and markdown extraction without supporting operations like configuration, error handling, or advanced proxy management. This leaves obvious gaps for a server with 'Proxy' in its name, such as setting or testing proxy settings.