@kazuph/mcp-fetch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_FETCH_TIMEOUT_MS | No | Request timeout in milliseconds | 12000 |
| MCP_FETCH_MAX_REDIRECTS | No | Maximum number of redirects to follow | 3 |
| MCP_FETCH_MAX_HTML_BYTES | No | Maximum HTML response size in bytes | 2000000 |
| MCP_FETCH_MAX_IMAGE_BYTES | No | Maximum image response size in bytes | 10000000 |
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 | {} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| imageFetchA | 画像取得に強いMCPフェッチツール。記事本文をMarkdown化し、ページ内の画像を抽出・最適化して返します。 新APIの既定(imagesを指定した場合)
パラメータ(新API)
旧APIキー(enableFetchImages, returnBase64, saveImages, imageMax*, imageStartIndex 等)は後方互換のため引き続き受け付けます(非推奨)。 Examples(新API) { "url": "https://example.com", "images": true } { "url": "https://example.com", "images": { "output": "both", "layout": "both", "maxCount": 4 } } Examples(旧API互換) { "url": "https://example.com", "enableFetchImages": true, "returnBase64": true, "imageMaxCount": 2 } |
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 one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.
The single tool name 'imageFetch' is descriptive and follows a verb_noun pattern. There is no inconsistency since only one tool exists.
While the server has only one tool, it is a complex and well-documented tool that handles a wide range of functionality appropriate for its fetch-image purpose. The count is slightly below the typical range but not insufficient.
The tool comprehensively covers fetching web pages, extracting images, and outputting them in various formats (base64, file, merged, individual). It includes parameters for text extraction and security, leaving no apparent gaps for its stated purpose.