MCP Server for Stealth Web Search and Fetching
Related Servers
Alternatives to MCP Server for Stealth Web Search and Fetching
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP 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.44 npmMIT
- AlicenseAqualityBmaintenanceA local-first MCP server that lets AI agents read any webpage as clean Markdown, crawl whole sites within configured limits, search without API keys, and solve supported captchas locally — all without cloud services or third-party keys.3020AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceA hardened local browser MCP server that drives your existing Chrome over the DevTools Protocol, providing token-efficient Markdown extraction and stealth features to avoid trivial automation detection.17 npm1MIT
- AlicenseAqualityBmaintenanceMCP server for browser automation with anti-detection. Scout pages, find elements, interact with websites, and monitor network traffic from any AI client that supports the Model Context Protocol.211MIT
- AlicenseNot gradedqualityCmaintenanceA production-ready Model Context Protocol server that brings AI-powered web search directly into development environments, providing intelligent search results with proper citations in Claude Desktop, Cursor, or any MCP-compatible client.106 npm21MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.1MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: websearch performs discovery (querying DuckDuckGo/Google), while webfetch retrieves and renders a specific URL. There is no plausible overlap or confusion between searching and fetching.
Both names follow the identical 'web' + verb convention (websearch, webfetch) in consistent lowercase with no separator. The pattern is fully predictable across the set.
Two tools is minimal but well-matched to a narrow search-and-fetch domain, where each tool maps to a core operation. It is slightly thin (no batch or pagination-control tool), but nothing feels redundant.
Search plus JavaScript-capable fetch with pagination covers the essential lifecycle of web retrieval, and the fetch tool handles content normalization. Minor gaps exist around result-count/format control, but core workflows are fully served.