NetLens
Allows performing web searches using DuckDuckGo, returning real result links (title, URL, snippet) via the web_search tool.
Allows performing web searches using Mojeek, an independent search index, returning real result links (title, URL, snippet) via the web_search tool.
Allows performing web searches using a SearXNG instance (self-hosted or public), returning result links, answers, infoboxes, and suggestions via the web_search tool.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NetLens fetch the full text of https://en.wikipedia.org/wiki/MCP"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
NetLens
An MCP server for unobstructed web reading. It fetches any URL directly with
browser-like headers — past robots.txt and naive bot blocks — and returns the
full page as clean, ad-stripped Markdown, not a summary. Plus web search that
returns real links. Zero dependencies: pure Python standard library.
Built for AI Agents
AI agents constantly hit pages their built-in tools can't read. NetLens fixes the three usual reasons a fetch comes back empty or useless:
Native web tools | NetLens |
Honor | Reads like the browser you'd open yourself — doesn't consult |
Blocked by header/User-Agent bot filters ( | Sends real browser headers via the system |
Return a summary of the page | Returns the full page content as Markdown |
Leave ads, cookie banners, nav, and related-links chrome in the output | Strips boilerplate locally so only the content reaches your context |
It does not try to defeat JavaScript/Cloudflare challenge pages or CAPTCHAs — that's out of scope by design. When a page is a hard block, the HTTP status is surfaced honestly rather than faked.
Related MCP server: Scrapi MCP Server
Installation
npm (via npx):
{
"mcpServers": {
"netlens": {
"command": "npx",
"args": ["-y", "netlens-mcp"]
}
}
}PyPI (via uvx):
{
"mcpServers": {
"netlens": {
"command": "uvx",
"args": ["netlens-mcp"]
}
}
}Add either to your MCP client config (e.g. .mcp.json for Claude Code), then
restart the session so the tools load.
Tools
web_search
Search the web and return real result links (title, URL, snippet), parsed locally —
links, not summaries. Follow up with web_fetch to read a result.
Argument | Type | Description |
| string (required) | The search query |
| integer | Optional cap; default returns the full first page (~10) |
| string |
|
| integer | Result page, 1-based. SearXNG only |
| string |
|
| string | e.g. |
The result reports which engine answered and what happened to any that were skipped, so falling through to a different backend is visible rather than silent:
{
"query": "…",
"engine": "mojeek",
"results": [ … ],
"engines_skipped": [ { "engine": "duckduckgo", "outcome": "HTTP 202" } ]
}Outcomes are observations, not conclusions — HTTP 202 is what the server sent;
whether that is throttling, changed markup or genuinely no matches cannot be
determined from the response. With SearXNG configured, direct answers,
infoboxes and suggestions appear alongside the results.
A search fetches a single result page (~10 results), returned in full by default so nothing at position 9/10 is dropped. There's no deep pagination — if the answer isn't in the first page, refine the query.
web_fetch
Fetch any page and return its full content as clean Markdown.
Argument | Type | Description |
| string (required) | URL to fetch (scheme optional; |
| string |
|
| string | Return only this heading's content, plus anything nested under it |
| string |
|
| integer | Optional cap on returned characters (truncates with a note) |
Reading part of a long page
A large article can be tens of thousands of characters when you want one part of
it. mode="outline" returns its shape, and section returns just that piece —
on a large encyclopedia article that is 153,000 characters full, 1,000 as an
outline, and 7,400 for the section actually wanted.
web_fetch(url=…, mode="outline") → headings with each section's size
web_fetch(url=…, section="Gameplay") → that section and its subsectionsOn link-heavy pages the URLs themselves are a large share of the output — around 40%
of a big encyclopedia article — so links="none" roughly halves it when you only need
the prose. Links pointing back into the same page are always rendered as plain text.
If a page turns out to be a client-rendered shell, web_fetch says so rather than
returning an empty result as a success:
(note: Only 10 characters of readable text were found in 6,856 characters of HTML. This page appears to be rendered client-side by JavaScript…)
Workflow: web_search to find pages, then web_fetch to read them.
Search engines
Search is a pluggable, selectable registry. In auto mode NetLens tries engines in
order and returns the first with results, so a rate-limit/challenge page on one
falls through to the next.
Engine | Notes |
| Default; |
| Automatic fallback |
| Independent index; automatic fallback |
| Self-hosted/public SearXNG JSON API — set |
Pick per call with the engine argument, or set a default with
NETLENS_SEARCH_ENGINE.
Configuration
Environment Variable | Default | Description |
|
| Default search backend |
| — | SearXNG base URL, e.g. |
|
| Seconds before an unreachable SearXNG is skipped |
| Chrome UA | Override the request User-Agent |
|
| Cap on a single response; larger ones are truncated |
|
| Seconds to reuse a fetched page; |
|
| Minimum seconds between requests to the same host |
|
| Ceiling on a single tool call |
Self-hosted SearXNG
Point NETLENS_SEARXNG_URL at an instance with the JSON API enabled (search.formats
must include json in its settings.yml). It is then tried first in auto mode,
which removes the HTML scraping — and the rate limiting that comes with it — from the
common path.
Because it is tried first, it must fail fast when the box is off: the connect timeout is bounded separately so an unreachable instance is skipped in a few seconds rather than stalling every search, and the skip is reported in the result.
How it works
Direct fetch. Requests go straight to the target site via the system
curl(better TLS/HTTP-2/compression, so it looks like a real browser), falling back tourllib. No third-party proxy or reader is involved.Local conversion. HTML → Markdown happens in-process with a hand-rolled
html.parserconverter — headings, lists, links (relative URLs resolved), code blocks, and GFM tables with colspan/rowspan.Content selection, not deletion. NetLens picks the page's main content region — the HTML5 landmark (
<main>/<article>/[role=main]) when one exists, otherwise the subtree holding the most prose relative to its link density — and converts only that. Because it selects a winner rather than deleting anything that matches a name pattern, extraction cannot silently return an empty page. Nothing inspects CSS class or id names to decide what is content.Pruning by measurement. Within that region, blocks that are overwhelmingly link anchors (navboxes, tag clouds, "more from this site" grids) are dropped based on their link density. Non-rendering elements (
<script>,<style>, …), explicitly hidden elements, and third-party ad-network slots (identified by vendor names likeadsbygoogle, which cannot collide with real prose) are removed outright.Response charset is honored (from
Content-Typeor<meta>), so non-UTF-8 pages don't come back garbled.
Usage from the CLI
The server is also a plain script — handy for testing before a client loads it:
python -m netlens_mcp.server search "http caching best practices"
python -m netlens_mcp.server fetch https://example.com/article
python -m netlens_mcp.server full https://example.com # whole body
python -m netlens_mcp.server raw https://example.com # unconverted HTMLpython -m netlens_mcp runs the stdio MCP server; python -m netlens_mcp.server <cmd> runs the CLI.
Development
pip install -e ".[dev]"
python -m pytest # run the test suite
ruff check . # lintRequirements
Python 3.10+ (and the system
curl, which ships with modern Windows/macOS/Linux; falls back tourllibif absent)
License
Available Tools
2 toolsweb_fetchWeb Fetch (full page)ARead-only
Fetch ANY web page directly and return its FULL content as clean Markdown (not a summary). Uses browser-like headers to get past common bot filters that block naive/robots-respecting clients (e.g. 403/202 to non-browser clients). Requests go straight to the target site; HTML is converted to Markdown locally (no third-party proxy/reader). Content is found by selecting the page's main content region and pruning navigation rails, so surrounding chrome is left out without ever risking the article. mode='article' (default) returns that region; mode='full' keeps the whole page body; mode='raw' returns unconverted HTML. Does NOT solve full JS/Cloudflare challenge pages or CAPTCHAs.
Inputs: url (required), mode, links, section, +1 more.
web_searchWeb SearchARead-only
Search the web and return real result links (title, URL, snippet), parsed locally from a search engine's HTML endpoint via a direct, bot-bypassing fetch. Returns LINKS, not summaries — follow up with web_fetch to read a result's full content. Returns the full first page of results (~10); a search fetches one page, so refine the query rather than expecting deep pagination. WORKFLOW: web_search to find pages, then web_fetch to read them.
Inputs: query (required), page, limit, engine, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
web_search and web_fetch have clearly distinct purposes: one finds relevant URLs via search, the other retrieves full page content. The descriptions explicitly differentiate them and explain their complementary workflow, eliminating any ambiguity.
Both tools follow the consistent verb_noun pattern (web_search, web_fetch), making the naming predictable and easy to understand.
Only 2 tools is minimal, but for a narrow focus on web searching and fetching, it's plausible. However, it feels slightly thin for a general-purpose server, as many use cases might require additional tools.
The tool surface covers only search and fetch, lacking tools for pagination, saving results, or handling multiple search engines. This leaves obvious gaps for a comprehensive web research workflow, potentially causing agent failures.
Maintenance
Related MCP Connectors
Web scraping MCP server: any URL to Markdown or JSON, with JavaScript rendering and batch jobs.
MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API
Turn any public website into an MCP server for agents to search, read and navigate.
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Related MCP Servers
- AlicenseBqualityCmaintenanceAn MCP server that integrates with the SearXNG API to provide comprehensive web search capabilities with features like time filtering, language selection, and safe search. It also enables users to fetch and convert web content from specific URLs into markdown format.276 npm4MIT
- AlicenseAqualityDmaintenanceMCP server that converts URLs to clean Markdown/Text for LLM agents.555 npm5MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides web search scraping from DuckDuckGo (with Mojeek fallback) and URL content fetching as markdown/text or raw HTML.1ISC
- AlicenseNot gradedqualityCmaintenanceA public MCP server that lets AI agents read live web pages as clean Markdown, with tools to fetch, search, extract metadata, and extract links from URLs.1MIT