EnriWeb
Related Servers
Alternatives to EnriWeb
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for multi-engine web search and web page fetching, supporting parallel search, content extraction, and optional LLM-powered search summarization and deep search.4MIT

xngmcpofficial
AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes web_search and web_fetch tools, enabling web search via SearXNG and fetching readable public pages.1MIT- AlicenseAqualityDmaintenanceAn MCP server that fetches web pages and extracts clean, AI-usable context from them, enabling tools for link discovery, content search, and integrated fetch-and-search operations.56 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to search the web and extract clean Markdown content, with support for JavaScript rendering, structured data extraction, and screenshots.1-
- AlicenseNot gradedqualityCmaintenanceMCP server providing web search, fetch, and crawl capabilities for AI agents via the spider.cloud API, with caching, cost controls, and robust error handling.MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides AI assistants with web search and intelligence capabilities via the ihyee API. It allows users to search the web, fetch extracted content from URLs, and perform full browser rendering for JavaScript-heavy websites.3MIT
TDQS
Scored across 2 tools
web_fetch (retrieve/read content from a specific URL) and web_search (discover sources via query) have clearly distinct purposes with no overlap. An agent can trivially tell which one to use for a given task.
Both names follow the same verb_noun snake_case convention (web_fetch, web_search) and share a consistent 'web_' prefix. Fully predictable and readable.
Search + fetch is the canonical minimal pair for a web-access server, so both tools earn their place. However, 2 is on the thin side given the enormous functionality (PDF/Office extraction, Drive inventories, YouTube, JS rendering) packed into web_fetch alone, which could plausibly be split.
Search and fetch cover the core read lifecycle, but web_fetch explicitly tells the agent to 'pasar la misma URL a la herramienta de análisis de media' for full multipass analysis — yet no such tool exists in this set, creating a dead end. This dangling reference signals a missing operation.