Fetch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONIOENCODING | No | Character encoding setting to address timeout issues on Windows systems | utf-8 |
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 | Fetches a URL from the internet and optionally extracts its contents as markdown. Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fetch | Fetch a URL and extract its contents as markdown |
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 ambiguity or overlap between tools. The tool 'fetch' has a clear, singular purpose of retrieving and optionally processing web content.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'fetch' is straightforward and descriptive for its function.
One tool is too few for a server named 'Fetch MCP Server', which implies broader capabilities. While the tool is useful, the server feels thin and under-scoped, lacking complementary tools like caching, filtering, or handling different content types.
The tool provides basic fetch functionality but leaves significant gaps for a fetch-oriented server. Missing operations include error handling, retry mechanisms, advanced parsing options, or tools for managing fetched data (e.g., save, list, delete). This limits agent workflows.