web-mcp
Related Servers
Alternatives to web-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables production-grade web research through MCP, combining local SearXNG search with hosted fallback providers, fetch and crawl tools, summarization, and budget guardrails.7MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform grounded web research with injection resistance, claim verification, and cost-aware routing through MCP tools like web_search, fetch_url, extract_claims, and check_grounding.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform web searches with full content retrieval and multi-engine provenance, including trust scoring and local corpus persistence, via MCP integration.1 npm3Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform live web searches across 9 engines, scrape web pages into clean formats, and run agentic research with citations via MCP.115 PyPI3MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to run local-first web research: intent-routed search across independent engines with reranking, a multi-stage fetch/crawl ladder, and document extraction. Results come back as signed-cursor, citation-bearing evidence envelopes, with an optional separately enabled profile for browser click/type actions.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform web research over MCP: search with a real browser, fetch JS-rendered pages, download PDFs and convert them to Markdown, then search and page through large documents using bounded previews so the context window isn't flooded.BSD Zero Clause
TDQS
Scored across 4 tools
Each tool targets a distinct step: starting a session, searching, fetching a page, and recording an approval. The two research_-prefixed tools (start vs approve) are semantically different but share a prefix, which could cause minor momentary confusion.
All names use snake_case with a clear verb_noun pattern (research_approve, research_start, web_search, web_fetch). The only deviation is the mixed research_ vs web_ prefixes, which is cosmetic rather than confusing.
Four tools map cleanly onto the research workflow (start, search, fetch, approve) with no redundancy. Slightly lean but well-scoped; no obvious filler.
The core loop of session start, search, fetch, and approval is covered. Minor gaps like an explicit session-end or session-status operation exist but are not blocking for the described workflow.