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 with other tools. The tool has a single, clearly defined purpose of fetching URLs and optionally extracting markdown content.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'fetch' is simple, descriptive, and follows a clear verb-based pattern appropriate for its function.
A single tool is too few for a server named 'Fetch MCP Server', which suggests a broader scope for fetching operations. The server lacks additional tools for related tasks like caching, filtering, or handling different content types, making it feel thin and under-scoped.
The tool surface is severely incomplete for a fetching domain. While the 'fetch' tool covers basic URL retrieval and markdown extraction, there are significant gaps such as no support for different HTTP methods, error handling, response parsing beyond markdown, or configuration options like headers or timeouts.