mcp-server-fetch-rag
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_URL | No | Proxy URL for HTTP requests | |
| USER_AGENT | No | Custom User-Agent string | |
| IGNORE_ROBOTS_TXT | No | Ignore robots.txt restrictions (set to 'true' to enable) |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_ragA | Fetch URL and return relevant content. Optionally provide a query to find specific information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fetch_rag | Fetch a URL and extract relevant content chunks |
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 confusion between tools. The single tool 'fetch_rag' is distinct by default.
The single tool name follows a clear verb_noun pattern ('fetch_rag'). Consistency is trivially achieved with only one name.
The server contains only one tool, which falls into the borderline category for scope. While a single-purpose fetch/retrieve tool might be acceptable, it feels thin for a typical MCP server.
The tool covers a single operation: fetching a URL and optionally querying for specific information. There are potential gaps such as batch fetching or handling stateful RAG workflows, but for a basic use case it may suffice.