fetch-guard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchA | Fetch a URL and return clean, LLM-ready markdown with metadata and prompt injection scanning. Args: url: The URL to fetch. timeout: Request timeout in seconds. max_words: Optional word cap on extracted body content. strict: When True and high-risk injection is detected, the response is marked as an error. js: Use Playwright for JavaScript-rendered pages (requires playwright + chromium). links: Link extraction mode — "domains" (default) or "full" for all URLs with anchor text. auth_token: Bearer token for Authorization header (e.g. "my-api-key"). headers: Deprecated. Use auth_token instead. Custom HTTP headers to include in the request. Returns: A structured dict with url, body (markdown), metadata, links, risk_level, injection_matches, sanitization stats, and edge case info. |
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
There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose (fetch a URL into clean markdown) is crystal clear from the name and description.
With a single tool named 'fetch', there are no naming inconsistencies or convention clashes to worry about. The name is a simple, predictable snake_case verb.
A single tool is borderline thin even for a focused fetching server; batch fetching, multi-URL, or search-style operations are not exposed as separate tools. It compensates somewhat by folding many modes (js, links, strict, auth) into one richly parameterized tool.
The tool covers the core fetch lifecycle well, including content extraction, metadata, link modes, auth, and injection scanning. Gaps are minor: no batch/multi-URL fetch or search-style discovery, and it carries a deprecated 'headers' parameter that overlaps with 'auth_token'.