Tor Mcp

io.github.Shreyas-ProfilePublished by GitHub account Shreyas-Profilev0.1.0Updated Oct 24, 2026

Route HTTP requests through the Tor network. Rotating exit IPs, .onion support, no body logging.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant send HTTP requests through the Tor network, rotate exit IPs and reach .onion sites.

What you can do
  • Send HTTP requests (GET, POST, HEAD) through Tor and get back status, headers and body
  • Check the current Tor exit node IP and country
  • Force a fresh Tor circuit to change the exit IP
  • Probe whether a target URL is reachable through Tor with a HEAD request
When to use it
Useful when an assistant needs to fetch non-Cloudflare sites from a different country, reach .onion services, test your own site from several exit IPs, or work around IP-based rate limits on APIs that do not blocklist Tor. Not suitable for Cloudflare-protected major sites, which block Tor exits.
Requirements
A remote endpoint at tor.regiq.in with no local install. A Google sign-in and an MCP API key generated on the dashboard, sent as an Authorization Bearer header. Free tier is limited to 100 requests per day, 30-second timeouts, 10 MB response bodies and GET/POST/HEAD methods. Self-hosting via Docker is also described.
Before you install
The API key is a credential sent in the Authorization header; keep it private. Requests are routed through third-party Tor exit nodes, so traffic is visible to those nodes, and the service logs target host, method, status, duration and size (not full URLs, bodies, cookies or headers). Requests can write or change data on target sites via POST. Free-tier quotas apply.

Installation

In SourceWeft

  1. Open Tor Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Shreyas-Profile%2Ftor-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tor": {
      "type": "http",
      "url": "https://tor.regiq.in/api/mcp"
    }
  }
}

README

tor-mcp

Route HTTP requests through the Tor network from any MCP-compatible agent.

Live at tor.regiq.in · Free forever · Google sign-in

What it does

Gives Claude Desktop / Cursor / any MCP client four tools:

ToolWhat it does
tor_fetch(url, method?, headers?, body?)HTTP request through Tor; returns status/headers/body
tor_get_exit_ip()Current exit node IP + country (verified via check.torproject.org)
tor_new_circuit()Force a fresh Tor circuit (SIGNAL NEWNYM)
tor_check(url)HEAD probe — is target reachable through Tor?

Honest scope

Tor exit nodes are blocked by Cloudflare on most big-brand sites (Indeed, Google, Amazon, etc.). Use tor-mcp for:

  • Non-Cloudflare sites
  • Geo-hidden fetches (see a site from a random country)
  • .onion services
  • IP-based rate-limit circumvention on APIs that don't blocklist Tor
  • Testing your own site from N different exits

If you need to hit Cloudflare-protected sites, use browser-mcp instead — real Chrome from a fixed Hetzner IP works for most WAFs, and you can layer a residential proxy on top for the rest.

Setup

  1. Sign in with Google at tor.regiq.in
  2. Generate an MCP API key on your dashboard
  3. Add to Claude Desktop / Cursor:
json
{  "mcpServers": {    "tor": {      "url": "https://tor.regiq.in/api/mcp",      "headers": {        "Authorization": "Bearer <YOUR_KEY>"      }    }  }}

Limits (per API key, free tier)

  • 100 requests/day
  • 30s timeout per request
  • 10 MB response body cap
  • Methods: GET, POST, HEAD only

Higher quotas for aggregators — email [email protected].

Privacy

  • DNS resolves inside Tor (socks5h:// scheme) — no plaintext lookup from our host
  • We log: target host, method, response status, duration, size
  • We never log: full URLs, query strings, request bodies, response bodies, cookies, headers
  • Standard TorBrowser User-Agent sent by default

Self-host

bash
git clone https://github.com/globalion/tor-mcpcd tor-mcpcp .env.example .env  # fill indocker compose up -d --build

Then browse to http://localhost:3021.

License

MIT · Built by Shreyas · Shipped by Globalion

Source: README.md at commit 1b42bbb

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts