markfetch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARKFETCH_API_KEY | No | Your API key (optional; falls back to the demo tier) | |
| MARKFETCH_API_BASE | No | Override the API base URL |
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 |
|---|---|
| scrape_urlA | Fetch a web page and return its main content as clean, LLM-ready markdown. Use this to give the model the content of a URL. |
| screenshot_urlB | Capture a screenshot of a web page as a PNG image. |
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 2 tools
Each tool has a distinct output format and purpose: one returns clean markdown content, the other a PNG screenshot. While both accept a URL, there is no ambiguity about which to use based on the desired result.
Both tools follow the verb_noun pattern (scrape_url, screenshot_url), making the naming scheme predictable and consistent. No mixed conventions or vague verbs.
With only two tools, the server feels minimal but not unreasonable for its focused purpose. It is at the lower end of the typical range, so it is borderline but still acceptable.
The server covers the two primary ways to consume a web page—text content and visual capture. Minor potential additions like raw HTML or metadata extraction are absent, but these are not core to the stated markdown-focused purpose.