web-tools-mcp-server
Related Servers
Alternatives to web-tools-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA drop-in replacement for Claude's built-in web_search tool that automatically tracks usage and provides multiple search backends.-
- AlicenseNot gradedqualityDmaintenanceProvides web search and page fetching tools for third-party models (e.g., DeepSeek, Qwen, Kimi) in Claude Code, with configurable search backends, Markdown output, and safety boundaries.94 PyPI64MIT
- AlicenseAqualityBmaintenanceEnables web search via a real browser for any LLM, bypassing anti-bot measures without API keys.5MIT
- AlicenseNot gradedqualityDmaintenanceDrop-in MCP replacement for the built-in WebFetch tool. Adds domain-scoped custom HTTP headers via YAML config, with bot-block detection, HTML-to-text extraction, retries, proxies, and prompt-injection sanitization.2MIT
- AlicenseAqualityCmaintenanceAd-free web scraping and search exposed as 3 MCP tools. fetch_page, fetch_pages_batch, search_web. Works with Claude Desktop, Cursor, Cline.390 PyPI2MIT
- AlicenseAqualityAmaintenanceEnables agents to run Google-first web searches with Bing and Google News fallbacks, and to fetch web pages as markdown, text, or raw HTML through an enterprise proxy with corporate TLS validation. Provides proxy, TLS, browser, and connectivity diagnostics without requiring search-provider API keys.3AGPL 3.0
TDQS
Scored across 3 tools
Each tool has a distinct purpose: web_fetch retrieves a single page, web_bulk_fetch retrieves multiple pages in parallel, and web_search performs a web search. There is no overlap between these operations; even web_fetch and web_bulk_fetch are clearly differentiated by the number of URLs they handle.
All tool names follow a consistent verb_noun pattern with a web_ prefix: web_fetch, web_search, web_bulk_fetch. The naming is predictable and clearly indicates the action and resource, with 'bulk' correctly modifying the fetch verb.
With only three tools, the set is well-scoped for a web utility server. Each tool covers a distinct primary use case (single fetch, bulk fetch, search), and the size is appropriate without being bloated or too sparse.
The tool surface covers the core operations for the domain: searching the web and fetching one or multiple pages, with strategy options (auto/direct/jina) for different anti-blocking needs. No obvious gaps for typical web research workflows, as pagination via count/offset is available in web_search.