FreeWeb-MCP
Related Servers
Alternatives to FreeWeb-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables free, keyless web search across a rotating chain of public engines, conversion of fetched pages into clean markdown with code blocks intact, and domain-scoped documentation crawling. Runs locally over stdio with load limits, a disk cache, and SSRF protections against untrusted page content.6PolyForm Noncommercial 1.0.0
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search the web through configured providers and crawl pages or whole sites into clean Markdown or JSON, including authenticated crawls and STDIO/HTTP transport.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search the web through configured providers and crawl pages or entire sites into clean Markdown or JSON, including authenticated crawls, over STDIO or HTTP.-
- AlicenseAqualityBmaintenanceEnables local stdio access to DeepSeek Search/Fetch for web search, page extraction, bounded site discovery, code context, and asynchronous SQLite-backed research with secure credential storage.3MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to run web searches across self-hosted SearXNG and/or You.com in parallel and to crawl single pages or whole sites into clean, deduplicated Markdown or JSON. It runs locally via STDIO or HTTP MCP transports, supports authenticated crawls, and requires no API key when using SearXNG.-
- FlicenseNot gradedqualityAmaintenanceEnables LLM agents to drive full web crawling and scraping through conversation by exposing tools for fetching, extracting, crawling, and screenshotting over stdio or SSE.-
TDQS
Scored across 8 tools
Most tools have clearly distinct roles: search, fetch, map, and crawl target different web-access workflows. The main overlap is browse vs browse_evaluate, since both operate on a page and agents may need careful reading to know when to use managed page actions versus arbitrary JavaScript evaluation.
The set mixes simple verbs (search, fetch, map, crawl, browse) with compound names (browse_evaluate, crawl_status, crawl_cancel). The convention is readable but not consistent, especially the verb_verb browse_evaluate and crawl_* grouping.
Eight tools are well-scoped for a web search/fetch/crawl/browse server. Each tool has a plausible operational role, and the crawl lifecycle is split into start, status, and cancel without excessive fragmentation.
The surface covers search, URL discovery, fetching, crawling with status/cancel, and page browsing/evaluation. There are minor gaps such as no explicit crawl resume/list operation despite checkpoints being preserved, but core workflows are covered.