weblens-mcp
Related Servers
Alternatives to weblens-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to fetch any web page as clean markdown or screenshot it, turning URLs into LLM-ready context.21 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to fetch webpages locally, extract main content, and convert it into clean, token-efficient Markdown with preserved links. Supports configurable multi-page crawling, caching, robots.txt compliance, and optional chunking for downstream processing.MIT

JsonLink MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI agents to read any web page as clean Markdown, pull title/description/preview metadata, capture desktop, mobile, or full-page screenshots, and list every link or image on a URL. JavaScript-heavy pages are rendered in a real browser and blocked requests retried through a proxy, so agents can reach content they'd otherwise miss.558 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents to fetch and crawl webpages, strip noise, and convert content into clean Markdown while preserving links for token-efficient scraping.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, screenshot, or convert web pages to PDF using a real headless browser, turning any URL into clean Markdown, a visual image, or a print-ready document.82 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides browser-grade web access by rendering pages to markdown, taking screenshots, and fetching images using headless Chromium/Firefox (Playwright) and httpx.MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. Its purpose is clearly stated and unambiguous.
The tool name 'fetch_page' follows a clear snake_case verb_noun pattern. With only one tool, there is no inconsistency.
A single tool feels thin, especially for a server named 'weblens' which implies a boader web toolkit. However, as a focused page-fetching utility, the count is borderline rather than clearly insufficient.
The core operation of fetching and rendering a web page to a local markup file is fully covered. Minor gaps exist like lack of options for custom headers or alternative output formats, but no critical lifecycle is missing for this narrow domain.