Proxlane

io.github.proxlane由 GitHub 帳號 proxlane 發布v0.1.2更新於 Oct 30, 2026

Web fetch for agents through your own Proxlane gateway. Block pages come back as failures.

概覽

AI 產生的概覽

為助理提供一個網頁擷取工具,透過自架的 Proxlane 閘道取得頁面,並把封鎖頁面當成失敗回報。

可以做什麼
  • 透過 Proxlane 閘道擷取網頁,取回可讀文字或 HTML
  • 可先執行頁面 JavaScript 或等待指定 CSS 選擇器再擷取內容
  • 可指定國別代碼並限制回傳長度,過長內容會被截斷並註明
  • 失敗時回傳結構化結果,說明結果類型、錯誤類別以及是否值得重試
適用情境
適合需要讓助理讀取網頁,並希望把封鎖頁或驗證碼頁視為錯誤、而非當成正文摘要的情境;前提是你已運行或打算運行具備供應商金鑰的 Proxlane 閘道。
執行需求
以 stdio 方式在本機執行,通常透過 npx 使用該 npm 套件。需要一個正在執行且至少設定一組供應商金鑰的 Proxlane 閘道,並以 PROXLANE_URL 提供閘道位址、以 PROXLANE_API_KEY 提供閘道本身的金鑰。需要能連線到該閘道的網路。
安裝前請注意
每次呼叫都會消耗供應商額度,使用 render 或 wait_for 時消耗高出數倍。PROXLANE_API_KEY 是閘道本身的金鑰,會放在行程環境變數中;請固定套件版本,因為未固定版本的 npx 會執行最後發佈的版本並帶著該金鑰。此工具刻意未標示為唯讀,用戶端可能因此跳出確認。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Proxlane,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

@proxlane/sdk

An MCP server that gives an AI agent a web-fetch tool that fails honestly.

A plain fetch hands an agent a 200 with a captcha in the body, and the agent summarises the captcha. This tool fetches through your own Proxlane gateway, which fails over between scraping APIs and checks every response for block pages. The agent gets the page as readable text, or a failure that says what happened and whether retrying is worth it. A block page is never returned as content.

Set up

You need a running gateway with at least one provider key. That is one container: proxlane.dev/docs/quickstart.

Then add the server to your MCP client. Claude Code:

bash
claude mcp add proxlane --env PROXLANE_URL=http://localhost:8787 --env PROXLANE_API_KEY=your-gateway-key -- npx -y @proxlane/[email protected]

Claude Desktop, Cursor and other clients take the same three things in their JSON config:

json
{  "mcpServers": {    "proxlane": {      "command": "npx",      "args": ["-y", "@proxlane/[email protected]"],      "env": {        "PROXLANE_URL": "http://localhost:8787",        "PROXLANE_API_KEY": "your-gateway-key"      }    }  }}

PROXLANE_API_KEY is the gateway's own key, not a provider's. Provider keys stay on the gateway. Pin the version, as above: npx -y otherwise runs whatever was published last, with that key in its environment.

Every call spends provider credits, several times more with render or wait_for. The tool is deliberately not marked read-only, so clients that auto-approve read-only tools still ask.

The tool

fetch_page

Argument
urlrequiredhttp or https
renderoptionalrun JavaScript first; costs several times more
wait_foroptionala CSS selector to wait for; implies render, and the page is a failure if it never appears
countryoptionaltwo-letter code, e.g. us
formattext (default) or html
max_charsdefault 20000longer results are truncated, and say so

On failure the result is marked as an error and reads:

json
{ "ok": false, "outcome": "SOFT_BLOCK", "class": "blocked", "retryable": true, "chain": "scraperapi:SOFT_BLOCK>brightdata:SOFT_BLOCK" }

class is one of six that never grows, and retryable follows from it: the site's own answer (target) and a bad request (client) are not worth retrying; a block or a provider problem may be, later. The gateway has already tried every provider it could, so an immediate retry is not.

In your own process

ts
import { createServer } from '@proxlane/sdk';import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
await createServer({ gatewayUrl: 'http://localhost:8787', apiKey: process.env.PROXLANE_API_KEY! })	.connect(new StdioServerTransport());

Apache-2.0.

來源:packages/sdk/README.md,提交 0f413a1

工具

1

fetch_page

Fetch a web page

Fetch a web page through a self-hosted Proxlane gateway, which fails over between scraping APIs and checks every response for block pages. Returns the page as text. On failure returns {ok:false, outcome, class, retryable, reason}: a blocked or captcha page is reported as a failure, never returned as content. Do not retry immediately when retryable is true; the gateway has already tried other providers.

輸入參數url必填formatrendercountrywait_formax_chars

版本歷史

2
  1. v0.1.2最新Oct 30, 2026
  2. v0.1.1Oct 26, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分