mcp-server-web-fetcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEB_FETCHER_MAX_BYTES | No | Per-response byte cap (10000–50000000). | 5000000 |
| WEB_FETCHER_TIMEOUT_MS | No | Default timeout (1000–120000). | 15000 |
| WEB_FETCHER_USER_AGENT | No | Outgoing User-Agent. | mcp-server-web-fetcher/<version> (+repo url) |
| WEB_FETCHER_CACHE_TTL_MS | No | Response cache TTL; 0 disables caching. | 60000 |
| WEB_FETCHER_MAX_REDIRECTS | No | Redirect hops allowed (0–20). | 5 |
| WEB_FETCHER_RESPECT_ROBOTS | No | Enforce robots.txt (RFC 9309 subset) before fetching. | false |
| WEB_FETCHER_CACHE_MAX_ENTRIES | No | Maximum cached responses. | 50 |
| WEB_FETCHER_ALLOW_PRIVATE_HOSTS | No | Set to true only to fetch localhost/LAN URLs on purpose. | 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_page_markdownA | Fetch a web page and convert it to clean Markdown for reading or analysis. Removes scripts, styles, ads and (by default) navigation chrome, resolves relative links to absolute URLs, and keeps tables, code blocks and lists intact. Long pages are paginated: when |
| extract_metadataA | Extract structured metadata from a web page without downloading it twice: title, meta description, canonical URL, language, author, publish dates, Open Graph and Twitter card tags, JSON-LD blocks, RSS/Atom feeds, hreflang alternates, the h1-h6 outline and the raw HTTP response headers. Use this to classify or summarise a page cheaply before fetching its full text. |
| extract_linksA | List the links on a web page as absolute URLs, each flagged as internal (same site) or external, with anchor text, title, rel and nofollow status. Supports scope filtering, de-duplication and a result limit — useful for crawling a documentation tree, auditing outbound links or finding next pages. |
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 3 tools
Each tool has a clearly distinct purpose: fetching and converting to markdown, extracting metadata, and extracting links. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (fetch_page_markdown, extract_metadata, extract_links), making them predictable.
Three tools is well-scoped for a web fetcher: one to get content, one for metadata, one for links. No unnecessary tools and the set feels complete for the domain.
The tool set covers the main needs of a web fetcher: retrieving content, extracting metadata, and listing links. There are no obvious gaps for typical use cases.