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 分