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 分