fetch-guard
Related Servers
Alternatives to fetch-guard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for AI agents -- fetch any URL with full JavaScript rendering (Playwright/Chromium) and convert to clean, token-efficient markdown. Works on React, Vue, Angular, and any JS-heavy page. Includes web search, batch fetching, binary file download, LRU cache, SSRF protection, and structured output.6 npmMIT
- AlicenseAqualityCmaintenanceA fast, dependency-light MCP server that converts web pages into clean Markdown, structured metadata, and classified links for language models.319 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that fetches web pages and extracts clean, AI-friendly Markdown content using Mozilla Readability. It provides secure web access for LLMs with built-in SSRF protection and automated content cleaning for improved context retrieval and summarization.1107 npmMIT
- AlicenseAqualityCmaintenanceMCP server that converts URLs to clean Markdown/Text for LLM agents.532 npm5MIT
- AlicenseAqualityBmaintenanceWeb extraction MCP server for AI agents. Extract structured data from any URL with built-in Cloudflare bypass, JavaScript rendering, and intelligent parsing. Returns clean markdown or JSON.5794 npm2MIT
- AlicenseAqualityAmaintenanceUltra-fast web fetcher and MCP server written in Rust. Fetches any URL as clean Markdown with HTTP/3, JavaScript rendering, anti-fingerprinting, browser cookie authentication from Chrome/Firefox/Brave, and 1Password integration.816MIT
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'.