MCP Fetch
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 | 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 single tool 'fetch' has a clear and distinct purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'fetch' is straightforward and appropriate.
One tool is too few for most server purposes, as it severely limits functionality and scope. While 'fetch' is useful, a server typically needs more tools to cover a meaningful domain effectively.
The server's purpose appears to be fetching web content, but with only one tool, the surface is severely incomplete. There are obvious gaps, such as no ability to handle errors, cache results, or manage different content types beyond markdown extraction.