mcp-local-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchB | Fetch content from a URL without following robots.txt restrictions. Returns the response body as text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly distinct by virtue of being the only one.
The single tool name 'fetch' follows a simple, common verb-only convention. With only one tool, there is no pattern inconsistency to evaluate.
The server has only one tool, which feels thin for a typical MCP server. However, the narrow purpose—fetching URL content—makes a single tool plausible, though it borders on under-scoped.
For the stated domain of fetching URL content, the tool fully covers the core operation. There are no obvious missing actions like update or delete because the domain is inherently a single read-only operation.