NetLens

io.github.pzalutski-pixel由 GitHub 账号 pzalutski-pixel 发布v0.2.3更新于 Oct 25, 2026

Read any web page as clean, ad-stripped Markdown past robots.txt and bot blocks, plus web search.

概览

AI 生成的概览

NetLens 是一个本地 MCP 服务器,可将网页抓取为去除广告的整洁 Markdown,并提供返回真实链接的网页搜索。

可以做什么
搜索网页并返回真实结果链接(标题、网址、摘要),可按调用或默认选择搜索引擎,并报告被跳过的引擎。抓取任意网址并以整洁 Markdown 返回整页内容,支持 article、full、raw、outline 模式,或只取某个标题下的章节。可用字符上限截断输出,或在只需正文时去掉链接网址。识别客户端渲染的页面并如实提示,而不是把空结果当作成功。
适用场景
当助手自带的网页工具返回空页面、只给摘要而非全文,或输出夹杂广告和导航时适用。适合有选择地阅读长文章,以及先搜索再阅读的流程。
运行要求
通过 npx(netlens-mcp)或 uvx 以 stdio 在本地运行;需要 Python 3.10+ 和系统 curl,缺失时回退到 urllib。需要访问目标网站和搜索引擎的网络。可选环境变量:NETLENS_SEARCH_ENGINE 和 NETLENS_SEARXNG_URL(指向 SearXNG 实例),以及超时、缓存、大小和 User-Agent 设置。未声明认证。
安装前请注意
它有意不遵守 robots.txt,并发送类似浏览器的请求头以绕过机器人拦截,可能与网站条款或政策冲突。抓取的页面内容会进入助手的上下文,请求直接发往第三方网站。它不处理 CAPTCHA 或 JavaScript 挑战页。缓存和同主机请求间隔可配置。

安装

在 SourceWeft 中

  1. 打开 控制台中的 NetLens,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

NetLens

[npm] [PyPI] [CI] [License: Apache 2.0] [Python 3.10+]

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 toolsNetLens
Honor robots.txt, so crawler-disallowed pages return nothingReads like the browser you'd open yourself — doesn't consult robots.txt
Blocked by header/User-Agent bot filters (403/202 to non-browser clients)Sends real browser headers via the system curl; commonly turns 403 → 200
Return a summary of the pageReturns the full page content as Markdown
Leave ads, cookie banners, nav, and related-links chrome in the outputStrips 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.

Installation

npm (via npx):

json
{  "mcpServers": {    "netlens": {      "command": "npx",      "args": ["-y", "netlens-mcp"]    }  }}

PyPI (via uvx):

json
{  "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.

ArgumentTypeDescription
querystring (required)The search query
limitintegerOptional cap; default returns the full first page (~10)
enginestringauto (default), duckduckgo, bing, mojeek, searxng
pageintegerResult page, 1-based. SearXNG only
time_rangestringday, week, month, year. SearXNG only
categoriesstringe.g. it, science, news. SearXNG only

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:

json
{  "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.

ArgumentTypeDescription
urlstring (required)URL to fetch (scheme optional; https assumed)
modestringarticle (main content only, default), full (whole body), raw (unconverted HTML), outline (heading structure)
sectionstringReturn only this heading's content, plus anything nested under it
linksstringinline (default) keeps link targets; none keeps link text but drops URLs
max_charsintegerOptional 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 sizeweb_fetch(url=…, section="Gameplay")  → that section and its subsections

On 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.

EngineNotes
duckduckgoDefault; html.duckduckgo.com endpoint
bingAutomatic fallback
mojeekIndependent index; automatic fallback
searxngSelf-hosted/public SearXNG JSON API — set NETLENS_SEARXNG_URL

Pick per call with the engine argument, or set a default with NETLENS_SEARCH_ENGINE.

Configuration

Environment VariableDefaultDescription
NETLENS_SEARCH_ENGINEautoDefault search backend
NETLENS_SEARXNG_URL—SearXNG base URL, e.g. http://192.168.1.10:8888
NETLENS_SEARXNG_TIMEOUT8Seconds before an unreachable SearXNG is skipped
NETLENS_USER_AGENTChrome UAOverride the request User-Agent
NETLENS_MAX_BYTES10485760Cap on a single response; larger ones are truncated
NETLENS_CACHE_TTL300Seconds to reuse a fetched page; 0 disables caching
NETLENS_HOST_DELAY0.5Minimum seconds between requests to the same host
NETLENS_REQUEST_TIMEOUT120Ceiling 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 to urllib. No third-party proxy or reader is involved.
  • Local conversion. HTML → Markdown happens in-process with a hand-rolled html.parser converter — 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 like adsbygoogle, which cannot collide with real prose) are removed outright.
  • Response charset is honored (from Content-Type or <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:

sh
python -m netlens_mcp.server search "http caching best practices"python -m netlens_mcp.server fetch  https://example.com/articlepython -m netlens_mcp.server full   https://example.com   # whole bodypython -m netlens_mcp.server raw    https://example.com   # unconverted HTML

python -m netlens_mcp runs the stdio MCP server; python -m netlens_mcp.server <cmd> runs the CLI.

Development

sh
pip install -e ".[dev]"python -m pytest        # run the test suiteruff check .            # lint

Requirements

  • Python 3.10+ (and the system curl, which ships with modern Windows/macOS/Linux; falls back to urllib if absent)

License

Apache License 2.0 — see LICENSE and NOTICE.

来源:README.md,提交 0cac036

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.2.3最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分