Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Region Fetch

by regionfetchversion 0.1.1i★ –iRuns on your computer
Registry namedev.regionfetch/mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: REGION_FETCH_WALLET_PRIVATE_KEY, REGION_FETCH_PAYMENT_SIGNATURE

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: REGION_FETCH_WALLET_PRIVATE_KEY, REGION_FETCH_MAX_PAYMENT, REGION_FETCH_BASE_URL, REGION_FETCH_PAYMENT_SIGNATURE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "regionfetch": {
      "command": "npx",
      "args": [
        "-y",
        "regionfetch-mcp"
      ],
      "env": {
        "REGION_FETCH_WALLET_PRIVATE_KEY": "your-value",
        "REGION_FETCH_MAX_PAYMENT": "your-value",
        "REGION_FETCH_BASE_URL": "your-value",
        "REGION_FETCH_PAYMENT_SIGNATURE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add regionfetch --env REGION_FETCH_WALLET_PRIVATE_KEY=your-value --env REGION_FETCH_MAX_PAYMENT=your-value --env REGION_FETCH_BASE_URL=your-value --env REGION_FETCH_PAYMENT_SIGNATURE=your-value -- npx -y regionfetch-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "regionfetch": {
      "command": "npx",
      "args": [
        "-y",
        "regionfetch-mcp"
      ],
      "env": {
        "REGION_FETCH_WALLET_PRIVATE_KEY": "your-value",
        "REGION_FETCH_MAX_PAYMENT": "your-value",
        "REGION_FETCH_BASE_URL": "your-value",
        "REGION_FETCH_PAYMENT_SIGNATURE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "regionfetch": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "regionfetch-mcp"
      ],
      "env": {
        "REGION_FETCH_WALLET_PRIVATE_KEY": "your-value",
        "REGION_FETCH_MAX_PAYMENT": "your-value",
        "REGION_FETCH_BASE_URL": "your-value",
        "REGION_FETCH_PAYMENT_SIGNATURE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • REGION_FETCH_WALLET_PRIVATE_KEY secret env
    Private key of a funded Base wallet. The server signs one fresh x402 authorization per tool call. Keep it in the host's env block; it is never a tool argument.
  • REGION_FETCH_MAX_PAYMENT env
    Per-payment ceiling, for example "$0.10". Use "off" to disable the cap.
  • REGION_FETCH_BASE_URL env
    Deployment origin.
  • REGION_FETCH_PAYMENT_SIGNATURE secret env
    A single pre-made x402 authorization. Funds exactly one request, so this is for one-shot testing only; prefer the wallet key.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain regionfetch.dev (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32476 servers in this category
  • Published to the registry more recently than 32% of the other 32476 servers in this category
  • Basic checks equal to or better than 100% of the other 32476 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Region Fetch safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: REGION_FETCH_WALLET_PRIVATE_KEY, REGION_FETCH_PAYMENT_SIGNATURE

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, zanadir

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

zanadir

by MustacheCase

Find what a repository's CI is missing, and which security checks cannot fail the build.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

npx -y regionfetch-mcp

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

Configuration

Wallet mode (recommended)
{

"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)
"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:

{

"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

Ask PopNx