mcp-fetch-ya
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| proxy_url | No | Proxy URL for requests | |
| user_agent | No | Custom User-Agent string | |
| ignore_robots_txt | No | Ignore robots.txt restrictions | false |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_yaA | If the built-in web fetch tool fails, you can retry with this MCP tool as a fallback. Fetches a URL and returns the content. HTML pages are converted to markdown for easier reading. |
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
Only one tool exists, so no possible confusion between tools. The purpose is clear: it fetches a URL as a fallback.
With a single tool, there is no inconsistency in naming. 'fetch_ya' follows a simple verb-based convention and is recognizable.
One tool is extremely minimal and may feel thin, but it exactly matches the narrow fallback-fetch scope. It sits in the borderline range for tool count.
For its stated purpose of acting as a fallback URL fetcher, the tool fully covers the operation: fetch, convert to markdown, and return content. No obvious gaps exist for this narrow domain.