Fetch public URLs as a visitor from specific countries with signed Ed25519 receipts to prove origin.
Also known as regionfetch/regionfetch, mcp, regionfetch-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.1
- Last commit
- Sep 1, 2026
- License
- MIT
What is Region Fetch MCP?
Region Fetch fetches public URLs as a visitor from specific countries with signed Ed25519 receipts to prove origin.
Summary generated from the project's README
About Region Fetch MCP server
Region Fetch provides a way to view public HTTPS URLs from the perspective of a visitor in specific countries. It uses a single tool called regionfetch to retrieve web content while providing a signed Ed25519 receipt that proves the origin of the request. This server is designed for developers who need to verify how websites appear in different geographic locations like the US, DE, JP, BR, or IN.
The server runs via stdio transport using Node 20.11 or higher. Users can set it up using npx or by configuring environment variables. For continuous use, the recommended wallet mode requires a REGION_FETCH_WALLET_PRIVATE_KEY and a REGION_FETCH_MAX_PAYMENT limit. A static signature mode is available for testing but only allows for a single request. The tool supports both http and browser modes for fetching data.
What you can do with it
- 1Verify regional website contentRequest a specific URL to see how it appears to a user located in Japan.
- 2Prove request originObtain a signed receipt to confirm the data was retrieved from a specific country.
- 3Test single request compatibilityPerform a one-shot check using a single pre-made authorization signature.
- 4Validate response integrityCheck that the returned body matches the signed receipt using the verification field.
Written from the project's README. Every use case is checked against a quote from it.
How to install Region Fetch MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Region Fetch MCP in Claude Code
$ claude mcp add --env 'REGION_FETCH_PAYMENT_SIGNATURE=<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>' --env 'REGION_FETCH_WALLET_PRIVATE_KEY=<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>' mcp -- npx -y regionfetch-mcpInstall Region Fetch MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"regionfetch-mcp"
],
"env": {
"REGION_FETCH_PAYMENT_SIGNATURE": "<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>",
"REGION_FETCH_WALLET_PRIVATE_KEY": "<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>"
}
}
}
}Install Region Fetch MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"regionfetch-mcp"
],
"env": {
"REGION_FETCH_PAYMENT_SIGNATURE": "<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>",
"REGION_FETCH_WALLET_PRIVATE_KEY": "<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>"
}
}
}
}Install Region Fetch MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","regionfetch-mcp"],"env":{"REGION_FETCH_PAYMENT_SIGNATURE":"<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>","REGION_FETCH_WALLET_PRIVATE_KEY":"<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>"}}'Install Region Fetch MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"regionfetch-mcp"
],
"env": {
"REGION_FETCH_PAYMENT_SIGNATURE": "<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>",
"REGION_FETCH_WALLET_PRIVATE_KEY": "<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>"
}
}
}
}Install Region Fetch MCP in Codex
$ codex mcp add mcp --env 'REGION_FETCH_PAYMENT_SIGNATURE=<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>' --env 'REGION_FETCH_WALLET_PRIVATE_KEY=<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>' -- npx -y regionfetch-mcpInstall Region Fetch MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "regionfetch-mcp"] [mcp_servers.mcp.env] REGION_FETCH_PAYMENT_SIGNATURE = "<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>" REGION_FETCH_WALLET_PRIVATE_KEY = "<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>"
Install Region Fetch MCP in Gemini CLI
$ gemini mcp add -s user -e 'REGION_FETCH_PAYMENT_SIGNATURE=<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>' -e 'REGION_FETCH_WALLET_PRIVATE_KEY=<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>' mcp npx -- -y regionfetch-mcpInstall Region Fetch MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"regionfetch-mcp"
],
"env": {
"REGION_FETCH_PAYMENT_SIGNATURE": "<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>",
"REGION_FETCH_WALLET_PRIVATE_KEY": "<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>"
}
}
}
}Configuration
REGION_FETCH_PAYMENT_SIGNATURESecretA single pre-made x402 authorization. Funds exactly one request, so this is for one-shot testing only; prefer the wallet key.
REGION_FETCH_WALLET_PRIVATE_KEYSecretPrivate 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_BASE_URLDeployment origin.
REGION_FETCH_MAX_PAYMENTPer-payment ceiling, for example "$0.10". Use "off" to disable the cap.
| Name | Description | |
|---|---|---|
| REGION_FETCH_PAYMENT_SIGNATURE | A single pre-made x402 authorization. Funds exactly one request, so this is for one-shot testing only; prefer the wallet key. | Secret |
| REGION_FETCH_WALLET_PRIVATE_KEY | 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. | Secret |
| REGION_FETCH_BASE_URL | Deployment origin. | |
| REGION_FETCH_MAX_PAYMENT | Per-payment ceiling, for example "$0.10". Use "off" to disable the cap. |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableregionfetch/regionfetch is public and reachablegithub.com/regionfetch/regionfetch ↗Pass
- Package names this repository as its sourceregionfetch-mcp names regionfetch/regionfetch as sourcenpmjs.com/package/regionfetch-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-01github.com/regionfetch/regionfetch ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from regionfetch-mcpPass
- No critical advisory in the package or its dependencies117 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubregionfetch-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
| Variable | Default | Purpose |
|---|---|---|
REGION_FETCH_BASE_URL |
https://regionfetch.dev |
Deployment origin. A trailing /api is stripped. |
REGION_FETCH_WALLET_PRIVATE_KEY |
— | Funded Base wallet key. Enables wallet mode. |
REGION_FETCH_MAX_PAYMENT |
$0.10 |
Per-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_MS |
120000 |
Per-request timeout. |
REGION_FETCH_ALLOW_INSECURE_HTTP |
0 |
Permit 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
toolscapability is advertised. No resources, prompts, or subscriptions are implemented or claimed.
Full documentation: https://github.com/regionfetch/regionfetch
MIT
Region Fetch MCP questions
How do I add Region Fetch MCP to Claude Code?
Run claude mcp add --env 'REGION_FETCH_PAYMENT_SIGNATURE=<YOUR_REGION_FETCH_PAYMENT_SIGNATURE>' --env 'REGION_FETCH_WALLET_PRIVATE_KEY=<YOUR_REGION_FETCH_WALLET_PRIVATE_KEY>' mcp -- npx -y regionfetch-mcp in your terminal. Add --scope user to make it available in every project.
How do I add Region Fetch MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How can I use the server for multiple requests?
Use Wallet mode by providing a funded Base wallet private key in the environment variables.
What countries are supported for fetching?
The tool currently supports the US, DE, JP, BR, and IN.
Can I use a single payment signature for testing?
Yes, you can use a static signature for one-shot compatibility checks, but the second tool call will fail.