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
} |
| experimental | {} |
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
With only a single tool, there is no possibility of confusion between tools. The tool's purpose and parameters are clearly described, making it easy for an agent to understand when to use it.
The single tool name 'fetch' follows a clear verb-only convention, which is consistent with common MCP naming practices. There are no other tools to introduce inconsistency.
One tool is borderline for a server; however, the fetch tool encapsulates a well-defined operation (fetching and sanitizing URLs) with rich parameters. The count is minimal but reasonable for a single-purpose server.
The fetch tool covers all necessary aspects of its domain: fetching, markdown conversion, prompt injection scanning, and flexible parameters (timeout, word cap, JS rendering, link extraction, auth). No obvious gaps for a URL-fetching server.