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 single tool 'fetch' has a clearly distinct and singular purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'fetch' is clear and follows a simple verb pattern.
One tool is too few for a server named 'Fetch MCP Server' that implies broader internet access capabilities. While the tool is useful, the scope feels thin, lacking complementary tools like search, filter, or validate URLs.
The tool surface is severely incomplete for internet access. It only fetches URLs and extracts markdown, missing essential operations like handling different content types, error handling for failed requests, or advanced features like caching or rate limiting.