Fetch MCP Server
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 tool's purpose is clearly defined and distinct.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.
A single tool is too few for most server purposes, making the set feel thin and limiting functionality. While the tool is well-defined, the server's scope appears minimal and could benefit from additional related operations.
The server's domain is fetching web content, but with only a basic fetch tool, there are significant gaps. Missing operations might include handling different HTTP methods, managing cookies or sessions, parsing specific content types beyond markdown, or error handling for network issues.