web-mcp
Related Servers
Alternatives to web-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables AI agents to search the web, fetch pages, and download images through a self-hosted proxy with Brave search, caching, and SSRF protection.51-
- AlicenseAqualityBmaintenanceLocal on-demand web search and page reading for coding agents via SearXNG, with SSRF-protected fetching and Markdown extraction.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to perform web searches and page fetching/crawling through self-hosted SearXNG and Crawl4AI, without depending on commercial search or scraping APIs.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run local multi-engine web searches, fetch pages through anti-bot fallback chains, and query site-specific sources such as GitHub, npm, PyPI, Docker Hub, and Twitter/X for structured results.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceProvides AI agents with a comprehensive web intelligence stack including crawling, private search via SearXNG, and intelligent RAG capabilities for focused content extraction. It supports advanced features like semantic vector search and knowledge graph integration for code validation to enhance AI performance and reliability.MIT
- AlicenseAqualityBmaintenanceEnables local LLMs to search the web and fetch clean content from URLs without API keys, using SearxNG and Mozilla Readability.239MIT
TDQS
Scored across 2 tools
web_search and read_page target clearly different actions (discovery vs. full-content retrieval) with no overlap in purpose. An agent can unambiguously pick the right tool based on whether it needs to find URLs or extract content from a known URL.
Both names use snake_case and concise English, but the conventions differ slightly: 'web_search' is a noun-prefixed verb while 'read_page' is a verb-noun pair. It is still readable and predictable enough that the minor deviation doesn't hinder selection.
Two tools is thin for a general-purpose web access server; search plus read is the minimal viable pair. It is defensible for the stated scope but leaves no room for adjacent operations, making it borderline under-scoped rather than well-provisioned.
The search-then-read lifecycle is fully covered, and the read tool handles HTML, PDF, text, JSON, retries, and truncation, which is thorough. Minor gaps exist (no multi-URL batch read or explicit raw/headers fetch), but agents can work around them via sequential calls.