Region Fetch

dev.regionfetch由 regionfetch.dev 发布v0.1.1更新于 Oct 24, 2026

Fetch any public URL as a visitor in a chosen country, with a signed receipt of its origin.

已验证STDIO仅桌面网页搜索与抓取金融

概览

AI 生成的概览

本地 MCP 服务器，以指定国家访客身份抓取公开 HTTPS 网址，并返回带签名的来源凭证。

可以做什么
通过单一 regionfetch 工具，以指定国家（US、DE、JP、BR 或 IN）的访客视角抓取公开 HTTPS 网址，可选普通 HTTP 或浏览器模式。返回上游状态码、响应体和 Ed25519 签名凭证，并在交给模型前用部署方公布的密钥和返回内容校验凭证。非 2xx 响应原样保留上游状态码与响应体，并标记为错误。付费请求最终失败时仍保留签名凭证，作为付费尝试的证据。
适用场景
适合需要查看某个公开页面或接口在特定国家的响应，并希望获得可验证的抓取来源证明的场景，例如核对地区性内容或区域可用性。若只是普通抓取、不关心地区与凭证，则无需使用。
运行要求
通过 npm 包 regionfetch-mcp 以 stdio 在本地运行，需要 Node 20.11 或更高版本。需要 REGION_FETCH_WALLET_PRIVATE_KEY 中已充值的 Base 钱包私钥（推荐），或 REGION_FETCH_PAYMENT_SIGNATURE 中一份预先生成的 x402 授权。可选配置包括 REGION_FETCH_BASE_URL、REGION_FETCH_MAX_PAYMENT、REGION_FETCH_RPC_URL、REGION_FETCH_TIMEOUT_MS 和 REGION_FETCH_ALLOW_INSECURE_HTTP。需要网络访问；README 标明为预发布版本，尚未发布到 npm。
安装前请注意
每次工具调用都要付费：服务器为每次调用签署一份 x402 授权，受 REGION_FETCH_MAX_PAYMENT 限制（默认 0.10 美元，设为 off 则取消上限）。需要已充值钱包的私钥，属于高价值机密；静态签名只能支付一次请求，第二次调用会失败。README 称密钥与授权不会作为工具参数传入，也不会写入输出，但私钥仍存放在宿主环境变量中。旧版变量名仍会被读取。

安装

在 SourceWeft 中

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

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

其他 MCP 客户端

参照 仓库 中的启动说明。

README

regionfetch-mcp

MCP server for Region Fetch — fetch a public HTTPS URL as a visitor in a specific country would see it, with a signed Ed25519 receipt proving where the retrieval came from.

Pre-release. Not yet published to npm. Build from source: https://github.com/regionfetch/regionfetch

bash
npx -y regionfetch-mcp

Node 20.11+. stdio transport. Exposes exactly one tool: regionfetch.

Configuration

Wallet mode (recommended)

json
{  "mcpServers": {    "regionfetch": {      "command": "npx",      "args": ["-y", "regionfetch-mcp"],      "env": {        "REGION_FETCH_BASE_URL": "https://regionfetch.dev",        "REGION_FETCH_WALLET_PRIVATE_KEY": "0x...",        "REGION_FETCH_MAX_PAYMENT": "$0.10"      }    }  }}

The server signs one fresh x402 authorization per tool call. This is the only configuration that keeps working past the first request.

Static signature (testing only)

json
"env": { "REGION_FETCH_PAYMENT_SIGNATURE": "<one x402 authorization>" }

One authorization funds one request, so the second tool call will fail. The server says so on stderr at startup. Useful for a one-shot compatibility check, not for a running server.

Wallet mode wins when both are configured.

Environment variables

VariableDefaultPurpose
REGION_FETCH_BASE_URLhttps://regionfetch.devDeployment origin. A trailing /api is stripped.
REGION_FETCH_WALLET_PRIVATE_KEY—Funded Base wallet key. Enables wallet mode.
REGION_FETCH_MAX_PAYMENT$0.10Per-payment ceiling. off disables it.
REGION_FETCH_PAYMENT_SIGNATURE—A single pre-made authorization.
REGION_FETCH_RPC_URL—RPC endpoint for on-chain reads during payment construction.
REGION_FETCH_TIMEOUT_MS120000Per-request timeout.
REGION_FETCH_ALLOW_INSECURE_HTTP0Permit an http:// base URL. Development only.

Legacy GEOFETCH_BASE_URL, GEOFETCH_PAYMENT_SIGNATURE, and PAYMENT_SIGNATURE are still read, with the canonical names taking precedence. Their use is reported as deprecated on stderr.

The tool

regionfetch — url (https, ≤ 2048 chars), country (US | DE | JP | BR | IN), mode (http | browser, default http).

Results use the v1 envelope:

json
{  "status": 200,  "ok": true,  "response": { "data": { "...": "..." }, "receipt": { "...": "..." } },  "verification": { "valid": true, "signatureValid": true, "bodyHashMatches": true }}

verification is an additive field: the server verifies each receipt against the deployment's published key and the returned body before handing it to the model. Consumers reading only status, ok, and response are unaffected.

Non-2xx responses keep the upstream status and JSON body verbatim and set isError: true. Terminal paid failures (502, 504) keep their signed receipts — they are the evidence the paid attempt happened.

Security

  • Wallet keys and payment authorizations are never accepted as tool arguments, never written to stdout or stderr, and never returned in tool output.
  • stdout carries JSON-RPC only; all diagnostics go to stderr through a redacting logger. Tests assert both.
  • Only the tools capability is advertised. No resources, prompts, or subscriptions are implemented or claimed.

Full documentation: https://github.com/regionfetch/regionfetch

MIT

来源：packages/mcp/README.md，提交 45ff6be

工具

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

版本历史

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

评分

已满足适用检查项的 50%

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

  • 近 30 天内可连通25 分

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

  • 已声明认证方式10 分

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

  • 已列出工具15 分

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

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