NetLens
PYPI · NETLENS-MCP · 2 COMPONENTS · SCANNED SEP 20
Read any web page as clean, ad-stripped Markdown past robots.txt and bot blocks, plus web search.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 667 tokens (~333/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the NetLens MCP server?
NetLens runs locally as a PyPI package, launched with uvx netlens-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · netlens-mcp
claude mcp add pzalutski-pixel-netlens -- uvx netlens-mcp
{
"mcpServers": {
"pzalutski-pixel-netlens": {
"command": "uvx",
"args": [
"netlens-mcp"
]
}
}
} {
"servers": {
"pzalutski-pixel-netlens": {
"command": "uvx",
"args": [
"netlens-mcp"
]
}
}
} codex mcp add pzalutski-pixel-netlens -- uvx netlens-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pzalutski-pixel-netlens": {
"type": "local",
"command": [
"uvx",
"netlens-mcp"
],
"enabled": true
}
}
} openclaw mcp add pzalutski-pixel-netlens --command uvx --arg netlens-mcp
mcp_servers:
pzalutski-pixel-netlens:
command: "uvx"
args: ["netlens-mcp"] {
"McpServers": {
"pzalutski-pixel-netlens": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"netlens-mcp"
]
}
}
} assistant mcp add pzalutski-pixel-netlens -t stdio -c uvx -a netlens-mcp
{
"mcpServers": {
"pzalutski-pixel-netlens": {
"command": "uvx",
"args": [
"netlens-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −2
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/netlens-mcp@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
web_fetch Web Fetch (full page) ~320
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.
| Name | Type | Req | Description |
|---|---|---|---|
| links | string | – | inline (default) keeps Markdown link targets; 'none' keeps link text but drops the URLs, which cuts a large share of the output on link-heavy pages |
| max_chars | integer | – | Optional cap on returned characters (truncates with a note); omit for full content |
| mode | string | – | article=main content only (default), full=whole body, raw=unconverted HTML, outline=heading structure with each section's size, for deciding what to request |
| section | string | – | Return only the section with this heading, plus anything nested under it. Matched case-insensitively on a substring. Use mode='outline' first to see what a long page contains. |
| url | string | yes | The URL to fetch (scheme optional; https assumed) |
No output schema declared.
No examples provided.
web_search Web Search ~272
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | string | – | SearXNG category filter, e.g. 'it', 'science', 'news'. SearXNG only. |
| engine | string | – | Search backend. 'auto' (default) tries SearXNG first when configured, then DuckDuckGo, Mojeek, Bing. 'searxng' needs NETLENS_SEARXNG_URL. |
| limit | integer | – | Optional cap on results; default returns the full first page (~10) |
| page | integer | – | Result page, 1-based. SearXNG only — the scraped engines serve one page and are reported as not supporting this rather than ignoring it. |
| query | string | yes | The search query |
| time_range | string | – | Restrict to recent results. SearXNG only. |
No output schema declared.
No examples provided.
What is the NetLens MCP server?
NetLens is an MCP server listed in the public MCP registry as io.github.pzalutski-pixel/netlens. Read any web page as clean, ad-stripped Markdown past robots.txt and bot blocks, plus web search. This page covers its PyPI package (netlens-mcp).
Is the NetLens MCP server safe to use?
NetLens scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the NetLens MCP server expose?
NetLens exposes 2 tools: web_search, web_fetch. Their descriptions and schemas cost roughly 592 tokens of context every time the server is loaded.
Is the NetLens MCP server still maintained?
NetLens is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the NetLens MCP server under?
NetLens declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.