Local, read-only onion search and text retrieval over Tor with content filtering.
Connect Runs on your machine
claude mcp add darkweb-mcp -e CONTENT_FILTER=<CONTENT_FILTER> -e ENGINES=<ENGINES> -e TOR_BRIDGES=<TOR_BRIDGES> -- docker run -i --rm ghcr.io/farbodghasemlu/darkweb-mcp:1.0.1
{
"mcpServers": {
"darkweb-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/farbodghasemlu/darkweb-mcp:1.0.1"
],
"env": {
"CONTENT_FILTER": "<CONTENT_FILTER>",
"ENGINES": "<ENGINES>",
"TOR_BRIDGES": "<TOR_BRIDGES>"
}
}
}
}
{
"mcpServers": {
"darkweb-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/farbodghasemlu/darkweb-mcp:1.0.1"
],
"env": {
"CONTENT_FILTER": "<CONTENT_FILTER>",
"ENGINES": "<ENGINES>",
"TOR_BRIDGES": "<TOR_BRIDGES>"
}
}
}
}
{
"servers": {
"darkweb-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/farbodghasemlu/darkweb-mcp:1.0.1"
],
"env": {
"CONTENT_FILTER": "<CONTENT_FILTER>",
"ENGINES": "<ENGINES>",
"TOR_BRIDGES": "<TOR_BRIDGES>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
CONTENT_FILTEROptional | Default content filtering for all tools |
ENGINESOptional | Comma-separated engine identifiers, or all |
TOR_BRIDGESOptional | Bridge lines separated by newlines or semicolons |
Details
| Package | ghcr.io/farbodghasemlu/darkweb-mcp:1.0.1 (OCI, stdio) |
| First published | 14 Oct 2026 |
| Last updated | 14 Oct 2026 |
| Registry name | io.github.farbodghasemlu/darkweb-mcp |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
