mcp-safe-fetch
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 |
|---|---|
| fetch_cleanB | Fetch a URL and return injection-sanitized, size-capped text. Args: url: an http/https URL to fetch. max_chars: per-fetch character cap (clamped to a hard ceiling). Returns a dict with the cleaned content and an audit of what was done. |
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
Only one tool exists, so there is no ambiguity at all. An agent cannot misselect between tools.
With a single tool, naming is trivially consistent. The name 'fetch_clean' follows a clear verb_noun pattern.
One tool feels thin for a server dedicated to fetching content. While the tool is well-defined, the server would benefit from additional tools (e.g., batch fetch, status check) to justify its scope.
The tool covers the core fetch-and-sanitize operation completely for a single URL. Minor gaps exist (e.g., no way to fetch multiple URLs or configure sanitization levels), but the basic use case is fully served.