原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Webshift

作者:x-monk版本 0.2.9i★ –i–
注册名称io.github.x-monk/webshift

安装

概览

作者提供的说明(英文原文)

Rust MCP server for denoised web search — fetch, clean, and rerank web content for AI agents.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: –
  • 传输方式:
  • 分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

作者没有在注册中心列出安装信息。请查看下方作者的 README。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 x-monk 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 7251 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 7251 个服务器的 7% 更新
  • 基础检查结果等于或优于此分类中其他 7251 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Webshift 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.2.9)于7个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。

有什么可以替代它?

同一分类中有:Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者:upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT今天更新
安装

Codebase Memory

作者:DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT20天前更新
安装

Exa

作者:exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT上个月更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

WebShift


What is WebShift

WebShift is a Rust library and MCP server that shifts noisy web pages into clean, right-sized text for LLM consumption.

Raw HTML is mostly junk: scripts, ads, navigation menus, cookie banners, tracking pixels. Feeding it directly to an LLM floods the context window with tens of thousands of useless tokens and leaves no room for reasoning. WebShift strips all that noise, sterilizes the text, and enforces strict size budgets so the model receives only the content that matters.

What you get

Depending on the features you enable, WebShift can be four things:

Use caseCrateFeature flagsWhat it does
HTML denoiserwebshiftdefault-features = falseclean() — pure Rust HTML-to-text pipeline. Strips noise elements, sterilizes Unicode/BiDi, collapses whitespace. Zero network, zero config. Drop into any Rust project that processes web content for LLMs.
HTML text rewriterwebshiftfeatures = ["text-map"]extract_text_nodes() + replace_text_nodes() — extract individual text nodes from HTML, manipulate them (translate, rewrite, simplify), and rebuild the HTML with structure intact. Tags, attributes, and links are never touched.
Web content clientwebshiftdefault or features = ["llm"]fetch() + query() — streaming HTTP fetcher with size caps, 8 search backends, BM25 reranking, optional LLM query expansion and summarization. Full pipeline from search query to structured results.
MCP serverwebshift-mcpall featuresNative binary (mcp-webshift) that exposes webshift_query, webshift_fetch, and webshift_onboarding over MCP stdio. Single static binary, zero runtime dependencies.
When to use WebShift
  • You're building an AI agent that needs web search and you want clean, budget-controlled text — not raw HTML.
  • You're processing web pages in a Rust pipeline and need a reliable HTML-to-text cleaner that strips noise without losing real content.
  • You need an LLM to translate, rewrite, or simplify text inside HTML without corrupting the markup — text-map gives you a safe round-trip.
  • You want an MCP web search server that works as a single binary — no Python, no pip, no venv, no Docker (unless you want it).
  • You need hard guarantees on output size: per-page caps, total budget caps, streaming download limits.
When NOT to use WebShift
  • You need a headless browser that renders JavaScript-heavy SPAs. WebShift parses static HTML — it doesn't execute JS.
  • You need to render or screenshot a page preserving its visual layout. WebShift processes HTML structure but does not render CSS or compute layout. (Note: text-map does preserve the DOM structure for text rewriting use cases.)
  • You're building a web scraper that needs to navigate across pages, fill forms, or handle authentication flows.

How it works

Question

| +- (optional) LLM query expansion -> multiple search variants | +- Search via backend (SearXNG, Brave, Tavily, Exa, SerpAPI, Google, Bing, HTTP) | +- Deduplicate + filter binary URLs | +- Streaming fetch with per-page size cap | +- HTML cleaning -> plain text (noise elements, scripts, nav removed) | +- Unicode/BiDi sterilization | +- BM25 deterministic reranking | +- (optional) LLM-assisted tier-2 reranking | +- Budget-aware truncation across all sources | +- (optional) LLM Markdown summary with inline citations | +- Structured JSON output

For a detailed explanation of each pipeline stage, BM25 parameters, adaptive budget allocation, and real compression metrics see Under the Hood. For the full configuration reference (TOML, env vars, CLI args) see Configuration. For ready-to-use examples see Use Cases.


Installation

Binary (MCP server)
cargo install webshift-mcp

The binary is called mcp-webshift.

From source
cargo install --path crates/webshift-mcp
As a library
# Full pipeline (search + fetch + clean + rerank)

webshift = "0.2"

Cleaner + fetcher only (no search backends)

webshift = { version = "0.2", default-features = false }

Text-map only (extract/replace text nodes in HTML)

webshift = { version = "0.2", default-features = false, features = ["text-map"] }

Everything including LLM features

webshift = { version = "0.2", features = ["llm"] }


Quick start

1. Set up a search backend

The easiest option is SearXNG — free, self-hosted, no API key:

docker run -d -p 8080:8080 searxng/searxng

No Docker? Use a cloud backend — see Search backends.

2. Configure your MCP client
{

"mcpServers": { "webshift": { "command": "mcp-webshift", "args": ["--default-backend", "searxng"] } } }

That's it. The agent now has webshift_query, webshift_fetch, and webshift_onboarding.

For client-specific setup see docs/integrations/.


MCP tools

ToolDescription
webshift_queryFull search pipeline: search + fetch + clean + rerank + (optional) summarize
webshift_fetchSingle page fetch and clean
webshift_onboardingReturns a JSON guide for the agent (budgets, backends, tips)
webshift_query parameters
ParameterTypeDefaultDescription
queriesstring or listrequiredSearch query or list of queries
num_results_per_queryinteger5Results per query
langstringnoneLanguage filter (e.g. "en")
backendstringconfig defaultOverride search backend

Configuration

Resolution order (highest priority first):

  1. CLI args — --default-backend, --brave-api-key, etc.
  2. Environment variables — WEBSHIFT_* prefix
  3. Config file — webshift.toml (current dir, then ~/webshift.toml)
  4. Built-in defaults
Config file
[server]

max_query_budget = 32000 # total char budget across all sources max_result_length = 8000 # per-page char cap max_total_results = 20 # hard cap on results per call max_download_mb = 1 # streaming cap per page (MB) search_timeout = 8 # seconds results_per_query = 5 oversampling_factor = 2 adaptive_budget = "auto" # "auto" | "on" | "off" — budget allocation mode

[backends] default = "searxng"

[backends.searxng] url = "http://localhost:8080"

[backends.brave] api_key = "BSA-..."

[backends.tavily] api_key = "tvly-..."

[backends.exa] api_key = "..."

[backends.serpapi] api_key = "..." engine = "google" # google | bing | duckduckgo | yandex

[backends.google] api_key = "..." cx = "..." # Custom Search Engine ID

[backends.bing] api_key = "..." market = "en-US"

[backends.http] url = "https://my-search.example.com/api/search" query_param = "q" count_param = "limit" results_path = "data.items" # dot-path to results array in JSON response title_field = "title" url_field = "link" snippet_field = "description"

[backends.http.headers] "Authorization" = "Bearer my-token"

[llm] enabled = false base_url = "http://localhost:11434/v1" # OpenAI-compatible api_key = "" model = "gemma3:27b" timeout = 60 expansion_enabled = true summarization_enabled = true llm_rerank_enabled = false

For every setting with all three config methods (TOML, env vars, CLI args) and plain-language descriptions, see the full Configuration Reference. Ready-to-use config examples are in Use Cases and examples/.

Key environment variables
WEBSHIFT_DEFAULT_BACKEND=searxng

WEBSHIFT_SEARXNG_URL=http://localhost:8080 WEBSHIFT_BRAVE_API_KEY=BSA-xxx WEBSHIFT_GOOGLE_API_KEY=xxx WEBSHIFT_GOOGLE_CX=xxx WEBSHIFT_BING_API_KEY=xxx WEBSHIFT_LLM_ENABLED=true WEBSHIFT_LLM_BASE_URL=http://localhost:11434/v1 WEBSHIFT_LLM_MODEL=gemma3:27b


Search backends

BackendAuthNotes
SearXNGnoneSelf-hosted, free. Default: http://localhost:8080
BraveAPI keyFree tier. brave.com/search/api
TavilyAPI keyAI-oriented. tavily.com
ExaAPI keyNeural search. exa.ai
SerpAPIAPI keyMulti-engine proxy (Google, Bing, DDG...). serpapi.com
GoogleAPI key + CXCustom Search. Free: 100 req/day. programmablesearchengine.google.com
BingAPI keyWeb Search API. Free: 1,000 req/month. Microsoft Azure
HTTPconfigurableGeneric REST backend — no code required, TOML-only config

LLM features (optional)

All opt-in — disabled by default, no data leaves your machine unless enabled.

FeatureWhat it does
Query expansionSingle query -> N complementary search variants
SummarizationMarkdown report with inline [1] [2] citations
LLM rerankingTier-2 reranking on top of deterministic BM25

Cross-language normalization (bonus): when BM25 reranking surfaces pages in

foreign languages (e.g. Chinese, Japanese, Arabic), the LLM summarizer still

produces the final report in the prompt language. The agent receives clean,

readable output regardless of the language mix in the source pages.

Works with any OpenAI-compatible API (OpenAI, Ollama, vLLM, LM Studio, etc.):

[llm]

enabled = true base_url = "http://localhost:11434/v1" model = "gemma3:27b"


Anti-flooding protections

Always active — the core value proposition:

ProtectionDescription
max_download_mbStreaming cap — never buffers full response
max_result_lengthHard cap on characters per cleaned page
max_query_budgetTotal character budget across all sources
max_total_resultsHard cap on results per call
Binary filter.pdf, .zip, .exe, etc. filtered before any network request
Unicode sterilizationBiDi control chars, zero-width chars removed

Library usage

use webshift::{Config, clean, fetch, query};

// Clean raw HTML — cap output at 8000

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx